Pure Rust, one toolchain
Every layer — from RTPS over DCPS to bridges and CORBA — is written in Rust. One toolchain, one set of build flags, one signed binary per platform.
Decide · warum?
Why ZeroDDS
The only complete OMG DDS implementation in pure Rust. Native RTPS 2.5 wire, full spec coverage from DDS 1.4 to DDS-Security 1.2, and the full CORBA 3.3 family — all under Apache 2.0, no per-seat fees, no commercial gate.
What is in scope
ZeroDDS is a full-stack OMG DDS implementation: protocols, language bindings, bridges, tooling. Here is what ships in the same workspace.
OMG specs implemented
Facts
Each fact links to evidence — file path, line number, or spec-coverage report.
Native RTPS 2.5 wire
ZeroDDS speaks RTPS 2.5 natively — the same OMG-standard wire protocol as Cyclone DDS, Fast DDS, RTI Connext and OpenDDS. Interoperability is verified end-to-end against Cyclone capture replays in CI.
Apache 2.0, no commercial gate
The full stack is Apache 2.0. No paid feature tier, no usage-based billing, no signing-bound runtime. Commercial support is a service, not a license.
Bridges everything, locks nothing in
Six first-class protocol bridges plus the full CORBA 3.3 family (20+ crates) ship in the same workspace as the core DDS stack.
Audit-ready by construction
Spec-coverage reports for every OMG document. Roughly 5,400 tests across the workspace. No claim on this site without a file path and a line number behind it.
Performance: on par
Raw RTPS wire and UDP transport are essentially identical to the established RTPS implementations. At full DCPS-pipeline our roundtrip is competitive with Cyclone, Fast DDS and RTI Connext on standard payloads. Methodology, payload sizes and tail-latency are documented on the comparison page.
How we compare
Side-by-side against three of the established RTPS implementations — ZeroDDS is the only pure-Rust column. The full nine-vendor matrix is linked below.
Source: official OMG vendor documentation and the vendors’ own release notes. Marked partial means a feature exists but is not fully spec-conformant.
Spec coverage
Every OMG specification we depend on is implemented end-to-end and tested. Coverage reports live at /spec-coverage/.
| OMG specification | Version | Status | Tests |
|---|---|---|---|
| DDS | 1.4 | 100% done | ~5,400 total |
| DDSI-RTPS | 2.5 | 100% done | 121 / 0 / 0 |
| XTypes | 1.3 | 100% done | full stack |
| DDS-Security | 1.2 | 100% done | 50 / 0 / 0 |
| DDS-RPC | 1.0 | 100% done | 94 / 0 / 0 |
| DDS-XRCE | 1.0 | 100% done | 82 / 0 / 0 |
| DDS-XML | 1.0 | 100% done | 73 / 0 / 0 |
| IDL | 4.2 | 100% done | parser + 7 codegen targets |
| DDS-PSM-Cxx | 1.0 | 100% done | 103 / 0 / 0 |
Where we stand today
ZeroDDS r1.0.0 rolls out crate by crate. Every crate ships with its own RC label and spec-coverage file.
Done · RC3
Every crate in the workspace carries a release-candidate marker. Each OMG specification ZeroDDS depends on — DDS 1.4, DDSI-RTPS 2.5, XTypes 1.3, DDS-Security 1.2, DDS-XRCE, DDS-RPC, DDS-XML, IDL 4.2, DDS-PSM-Cxx, DDS-Java-PSM — is implemented end-to-end, covered by tests, and backed by its own spec-coverage audit.
Spec-coverage reports →In flight
OMG Vendor-ID assignment in registry. Hardware-acceleration backends (DPDK / RDMA) on the bench. CCM container stack for financial-sector migration.
Open issues →Next · r1.0.0
r1.0.0 final after Vendor-ID arrives. Then quarterly minors. Long-term support branches start at r1.0.0. Public release notes per crate.
Release notes →Hard truths
No marketing without honest limits. Here is what ZeroDDS does *not* do today.
- OMG Vendor-ID pending. Until the OMG registry is updated, discovery packets carry a provisional vendor marker and are not cleared for production cross-vendor deployments. The RTPS 2.5 wire format itself is fully spec-conform; only the vendor_id field differs.
- Routing service: core shipped, advanced features maturing. ZeroDDS has a dedicated domain-routing service (zerodds-router) — the RTI Routing Service equivalent: it routes samples between domains, QoS profiles and topics with topic rename, multi-route fan-out, QoS mapping, SQL content filters and keyed-instance lifecycle, alongside the recorder, monitor and DDS-WEB gateway. Still maturing on top of that core: rate limiting, persistence-backed routes, multi-tenancy / ACL and cross-vendor routing-service interop.
- Hardware acceleration pending. DPDK / RDMA transports are on the bench, not in r1.0.0. For sub-microsecond paths you still want shared memory (iceoryx2-compatible) — which ships.
License & commercial support
Apache License 2.0 — the same license as Kubernetes, gRPC and most modern infrastructure software.
You can fork it, modify it, run it in any product, redistribute it, and you do not owe us a cent. Commercial support contracts cover SLA-bound incident response, on-call rotation, custom feature work, security audits and migration consulting. Pricing depends on scope, not seats.