Competitive Positioning
How Tinverse Compares
Compare Tin DDS and Retina against your workload and integration requirements. We can help prepare regulatory evidence packages scoped to your product and available engineering records.
We publish our measured performance, our raw delivery counters, and our explicit limitations. Where an incumbent is the better fit, we state it out loud.
Pillar 1
Evidence, Not Assurances
We can help organize software development, risk management, SOUP, and verification evidence for your regulatory evidence package.
Pillar 2
Engagement Scoped to Your Program
Contact us to discuss your intended use, integration needs, available materials, and commercial terms.
Pillar 3
Radical Transparency
Published latency distributions with loss counters, reproducible benchmark harnesses, and an explicit list of what we do not support.
Middleware Comparison Matrix
| Dimension | Tinverse (Tin DDS & Retina) | Other Market-Leading Commercial Vendors | Other Leading Open-Source Alternatives |
|---|---|---|---|
| Licensing Model | Commercial terms agreed for each engagement. | Proprietary binaries and seat licenses. | Open source (Apache 2.0 / EPL-2.0) with enterprise add-ons. |
| Regulatory & SOUP Dossier | Support preparing regulatory evidence packages, scoped to your product and available records. | DO-178C / ISO 26262 add-on packages (separate pricing tier). | Customer must perform complete SOUP qualification in-house. |
| Delivery Format | Delivery materials and access terms agreed for each engagement. | Proprietary closed-source binaries and headers. | Public source repository. |
| ROS 2 Compatibility | ROS-compatible CDR wire formats without shipping the ROS runtime, plus optional RMW. | Supported via vendor RMW adapters. | Default Tier 1 RMW implementations. |
| Interprocess Zero-Copy | Daemon-backed shared memory, descriptor queues, bounded loan lifecycle. | SHMEM transport (proprietary). | Requires iceoryx integration or data-sharing config. |
| Surgical Teleoperation | Deterministic 2-path command admission & fail-safe supervision. | Generic QoS / application-layer implementation required. | Application-layer implementation required. |
Head-to-Head Performance (ARM64 Linux, 64-Byte Sample, Reliable UDP)
Homogeneous pairs, two processes, 500 warm-up exchanges, 10,000 retained observations per run, 5 interleaved runs.
| Implementation | p50 One-Way | p99 One-Way | p99.9 One-Way | Exchanges/sec |
|---|---|---|---|---|
| Tin DDS 0.1.0 (C++) | 5.20 µs | 6.92 µs | 10.50 µs | 93,223 |
| Retina 0.1.0 (Rust) | 6.43 µs | 9.09 µs | 10.91 µs | 75,052 |
| Leading Open-Source Alternative B (0.10.4) | 16.36 µs | 18.65 µs | 77.42 µs | 30,006 |
| Leading Open-Source Alternative A (2.14.6) | 19.26 µs | 26.05 µs | 40.56 µs | 24,692 |
| Leading Commercial Vendor (7.7.0) | 22.00 µs | 34.00 µs | 156.00 µs | 22,464 |
*Note: Tests measure homogeneous pairs under identical host constraints. Separate 412 ns shared-memory measurements time the loan mechanism only and exclude serialization/RTPS framing.
What Tin DDS Does Not Support (Explicit Non-Goals & Gaps)
We believe in honest qualification. If your architecture depends on these features today, incumbent vendors are the correct choice:
- No WAN Routing / Cloud Traversal: Optimized for on-robot same-host and intra-machine real-time networks. Does not replace enterprise WAN routing services for global fleets.
- No Dynamic In-Flight Schema Evolution: TypeObject assignability is verified, but dynamic schema mutation on live topics is not supported.
- No SQL-Expression Compilation: Content filtering uses application-supplied typed predicates, not runtime SQL parsers.
- No PLC / Ladder IDE: We build for C++26 and Rust real-time systems, not IEC 61131-3 industrial controllers.
- EtherCAT Profile: Fixed single-bus chain (2–30 slaves, CiA-402 over CoE). No EoE, AoE, SoE, cable redundancy, or hot-connect groups.
Engineering Engagement
Discuss Your Program
Tell us about your target hardware, middleware requirements, and integration goals. We agree on scope, deliverables, access terms, schedule, and commercial terms for each engagement.
Discuss your requirements →Regulatory Evidence Support
We can help prepare regulatory evidence packages using your product requirements and available engineering records. Discuss the software development, risk management, SOUP, and verification evidence your team needs.
Discuss an evidence package →Prove It on Your Target in 48 Hours
Send us your message types, QoS constraints, or bus topology. In 48 hours, you receive a signed report showing your workload executing with raw p50/p99 latency, loss counters, and full caveats.
Request Your 48-Hour Bake-Off