Product

How DiodeGuard works.

A sender that only transmits, a receiver that only listens, and error correction in between that replaces every acknowledgement.

The idea

No return path means nothing to attack.

A normal network connection is a conversation: the receiver keeps saying "got it". An attacker on the receiving side can use that conversation to reach back in.

DiodeGuard removes the conversation. The sender fires data at the receiver and never listens. The receiver never writes back. Lost packets are repaired from extra data that travelled with the original, not by asking again.

HIGH network                          LOW network
 sender  ──▶  encode  ══ one-way ══▶  receiver
 reads        FEC + sign   UDP         repair + verify
 only         no ACKs                  deliver or
                                       quarantine
What moves

Files, databases and plant protocols.

Files

Watch a folder and send what lands in it. Each file is hashed end to end (SHA-256 or BLAKE3). It is delivered only if it verifies; anything else goes to quarantine.

Databases

SQL Server change data capture, or any database with an ODBC driver, replicated into SQL Server, PostgreSQL or SQLite. Ordered, exactly once, with snapshots when something is missing.

Industrial protocols

Modbus/TCP and OPC UA are polled on the high side with read requests only and re-published by a read-only server on the low side. MQTT, syslog, SNMP traps, HTTP, SMTP, TCP and UDP are mirrored too.

Built to be operated

The management console

Every setting has a plain-language explanation. Every change is validated by the real program before it is saved, versioned, and recorded.

Plain configuration

Simple wording, safe defaults, advanced options folded away.

Fleet view

Every diode, healthy or not, with live numbers, search, filters and paging.

Roles and audit

Viewer, operator and admin accounts and a tamper-evident audit log.

Self-check

A built-in checker finds the common mistakes before they cost you a day.

Performance

Measured, and published.

5.04 Gbit/s
best verified file throughput on two cloud VMs (about 10 Gbit/s on the wire including repair data)
Multi-lane
several parallel senders and sharded receivers for faster links
Raw data
every run, the exact test script, and an independent SHA-256 check are published
Next: 100G
a 100 Gbit test is planned; we publish results when they exist, not before

Cloud VMs are shared networks; plant networks and dedicated NICs behave differently. Run the built-in link test on your own path before you commit.

Ready to try it on your network?

Create an account and invite your team.

Get started