Commercial Services
ZeroDDS is Apache-2.0 open source — the entire stack, free for any use, in production, forever. There is no crippled "community edition" and nothing held back behind a paywall. Commercial services exist for one reason: to give teams running ZeroDDS in production a contractual engineering partner for guaranteed response, hardening, integration and migration.
If you are evaluating ZeroDDS for a long-lived, regulated or safety-relevant system, the questions are usually the same — who answers the phone when something breaks at 3 a.m., who signs off the security configuration, who owns the migration off your current vendor. The answers are below.
Open source, fully. Paid support, optionally.
Every line of ZeroDDS lives on GitHub and ships on crates.io under Apache-2.0 — the runtime, the security plugins, the bridges, the code generators, the conformance suite. You can read it, audit every unsafe block, run the full cross-vendor test matrix yourself, fork it, and self-support indefinitely with no licence and no permission. Commercial support never unlocks a feature. It buys you something the open-source licence cannot: guaranteed response, accountability, and dedicated engineering capacity.
Always free, no strings
- The complete OMG stack — DDS, RTPS, XTypes, Security, RPC, XRCE, the language PSMs.
- Production use, commercial use, redistribution — Apache-2.0, including a patent grant.
- Full source, full test suite, full documentation. No telemetry, no licence keys.
What support actually buys
- A contractual response time when production is down — not a best-effort issue queue.
- Engineers who know the internals doing the work you would otherwise staff for.
- Sign-off, documentation and traceability you can put in front of an auditor.
Support tiers
Community
Free
Public, best-effort support from the maintainers — the same channel the project itself runs on.
- GitHub Issues & Discussions
- Public roadmap and release notes
- Community-reviewed bug fixes
Professional
Contact us
For teams with ZeroDDS in production that need a predictable turnaround and a named contact.
- Guaranteed first response within one business day
- Private support channel, prioritised bug triage
- Quarterly architecture & QoS review
- Upgrade guidance and pre-release validation
Enterprise
Contact us
For regulated, safety-relevant or 24/7 systems where downtime and audit exposure carry real cost.
- 24/7 on-call with escalation path
- A dedicated engineer who knows your deployment
- Custom feature work on an agreed roadmap
- Source-level security audit
- CRA-grade compliance and traceability documentation
Response times, scope and pricing are agreed per contract — tell us your deployment, your uptime target and your compliance obligations, and we will propose a tier that fits.
Services
Fixed-scope engagements, delivered against a written statement of work. Each one ends with source, tests and documentation you own outright — never a black box.
Migration off your current vendor
Move from Cyclone DDS, OpenDDS, Fast DDS or RTI Connext onto ZeroDDS without a flag-day rewrite. ZeroDDS speaks native RTPS 2.5 and interoperates on the wire with the major vendors, so old and new nodes coexist on the same domain during the transition.
- QoS-profile and IDL translation, with diffs you can review
- Cross-vendor wire-interop verification against your real traffic
- Phased cut-over plan — coexist first, replace incrementally
Custom integrations
New transports, protocol bridges or platform ports built into the same codebase — not bolted on as an unmaintained side project.
- Proprietary fieldbus or transport layers
- Bridges to existing message buses and cloud back-ends
- Embedded / no_std and MCU targets, automotive and DO-178C-oriented profiles
Security audit & hardening
A focused review of how DDS-Security is actually configured in your deployment, with concrete, prioritised remediation.
- Governance, permissions and ACL hardening
- Key management and rotation review
- Cross-vendor secure-interop validation
Training & enablement
On-site or remote training that leaves your team able to operate ZeroDDS without us.
- DDS fundamentals and ZeroDDS architecture
- QoS design, performance tuning and troubleshooting
- Security configuration and type evolution
Built for regulated, long-lived systems
ZeroDDS is designed for the systems where middleware outlives the team that chose it: where you still need patches in ten years, where an auditor will read the source, and where vendor lock-in is an existential risk. That covers industrial automation, automotive, robotics and ROS 2, aerospace and defence, and energy and medical systems — anywhere a data bus has to be open, inspectable and supportable for the long haul.
Why ZeroDDS is a sound foundation to commit to
- Apache-2.0, no rug-pull. A permissive licence with a patent grant — not open-core bait that flips to a restrictive licence once you depend on it.
- Pure Rust. Memory safety by construction, with every remaining
unsafeblock carrying a written justification. - Full OMG spec coverage. DDS, RTPS, XTypes, Security, RPC, XRCE and the language PSMs — with a public, per-section coverage audit you can check yourself.
- No lock-in. Native RTPS 2.5 interoperates with Cyclone DDS, Fast DDS and RTI Connext, plus bridges to MQTT, AMQP, CoAP, gRPC, CORBA, ROS 2 and WebSocket.
- Audit-ready. Readable source, a full conformance suite, and documentation aimed at CRA and functional-safety review.
One honest caveat: an official OMG vendor ID is still pending. Until it is assigned, discovery packets carry a provisional marker — see the note on any spec-coverage page. Wire interop is otherwise in place today.
How an engagement works
- Scoping call. Tell us what you are building, which vendor you run today, and what you need. No sales funnel — an engineer, not a closer.
- Written proposal. A fixed scope, deliverables, timeline and price. You decide with everything in front of you.
- Delivery. Work happens in the open against the agreed scope, with regular check-ins and reviewable progress.
- Handover. Source, tests and documentation you own — plus an ongoing support tier if you want one.
FAQ
Is the open-source version limited compared to a paid one?
No. There is one ZeroDDS, Apache-2.0, complete. Support and services add people and guarantees, never features.
Do we need a commercial licence to ship ZeroDDS in production?
No. Apache-2.0 already permits production and commercial use, redistribution and modification, with a patent grant. A contract only buys support.
Do you do fixed-price engagements and sign NDAs?
Yes to both. Service work is scoped and priced up front, and we are happy to work under an NDA for anything that touches your systems or data.
Can you keep us interoperable with our existing DDS vendor?
That is the point of native RTPS 2.5 — ZeroDDS and your current vendor share a domain, so you migrate incrementally instead of in one risky cut-over.
Get in touch
Reach the ZeroDDS commercial team at hello@zerodds.org, or use the contact page. Tell us what you are building, the vendor you run today, and the spec coverage and uptime you need — we answer concrete questions, not marketing funnels.