NEW OPC UA, Modbus, SQL replication and file transfer in one platform

Data goes out.
Nothing comes back.

DiodeGuard moves data from your most trusted network to a less trusted one over a one-way path, with error correction instead of acknowledgements, so there is simply no return channel to attack.

Software on your own hardware. Pair it with transmit-only fibre or a unidirectional port for physical one-wayness.

HIGH control networkone-way gateLOW business network
SQL SERVER CDCOPC UAMODBUS/TCPMQTTSYSLOGFILES
5.04 Gbit/s
verified file throughput between two cloud machines, SHA-256 identical end to end
0
return packets: the sender never reads and the receiver never writes back
Exactly-once
database replication with an alarm, never silent drift, when anything is missing
1 afternoon
to install: static binaries, systemd units, a browser console
Why teams switch

Everything a data diode project needs,
without the appliance budget.

Hardware diodes are excellent and expensive. For most plants the harder part is the software on both sides. DiodeGuard is that software, done properly.

Fail-safe, not fail-open

Every file and every database batch is checked end to end. Anything that cannot be proven complete and authentic is quarantined, and the replica stops and raises an alarm instead of drifting.

Loss-tolerant by design

Reed-Solomon forward error correction, interleaving and optional double sending repair lost packets with no retransmission request, because there is no way to send one.

Real database replication

SQL Server change data capture, any ODBC database, or SQLite on the high side; SQL Server, PostgreSQL or SQLite on the low side. Ordered, exactly once, with automatic snapshot recovery.

A console people actually use

Plain-language configuration, a fleet view of every diode with live numbers, users and roles, an audit trail you can verify, and one-click rollbacks. No spreadsheet of command-line flags.

Fast enough to be boring

Multi-lane sending, kernel segmentation offload and sharded receivers. Measured, with the raw runs published, not a brochure number.

Your protocols, mirrored

Modbus, OPC UA, MQTT, syslog, SNMP traps, HTTP, SMTP and plain TCP and UDP, each with read-only behaviour on the low side so nothing can be written back.

How it works

Three pieces. No return path.

Read on the high side

A sender reads files, database changes or protocol values inside your trusted network. It only ever transmits.

Cross the one-way link

Data is split, numbered, signed and protected with repair packets, then sent as UDP over a transmit-only path. No acknowledgements exist.

Verify on the low side

The receiver rebuilds, repairs, and checks everything. Only data proven intact is delivered; the rest is quarantined with an alarm.

Read the full walkthrough

Honest by default

What we claim, and what we do not.

Security buyers hate surprises. So here is the plain version, before you ask.

What is true today

Protocol-level one-wayness with no return packets in the code. End-to-end integrity checks. Keyed authentication and replay protection. A hash-chained audit log. A published threat model, raw benchmark data, and test suites you can read.

What is not true yet

No certification, and no independent third-party penetration test or audit yet. Software cannot make a cable one-way: physical one-wayness comes from transmit-only fibre or a unidirectional port. We say so on every page that matters.

Put a one-way door on your network.

Create an account, invite your team, and be moving data in an afternoon.