— Proof
Built for production.
Five production verticals. Named protocol stacks. Standards you can look up independently.
Fleet-wide rollout on a flagship performance brand.
A leading performance-vehicle OEM ships MOS4 fleet-wide. Multi Stacks decodes the OEM-private CAN dialect; OBDStacks adds the proprietary PIDs; the on-device AI pipeline powers driver feedback. One ECU, one OS, one OTA channel.
Globally deployed ground-operations vehicles.
A global airport ground-operations manufacturer runs MOS4 on its specialty-vehicle fleet — telemetry over MD21, on-board observability via OpenTelemetry, and a remote-diagnostics workflow that reduced in-field debug time from days to hours.
Regional rollout of an ISOBUS-first programme.
An agricultural-machinery manufacturer ships ISOBUS-first equipment on MOS4. On-device inference models retrain on crop and asset data captured at field cadence; operator-grade dashboards run on the same box. ISOBUS acquisition is read-only (ISO 11783).
Off-highway-machine maker on the same OS as the road fleet.
An off-highway machinery maker uses MOS4 to unify its on-road and off-road programmes — Multi Stacks for J1939 + CAN-FD, ROI shader for the camera plane, signed OTA across both vehicle classes.
Modbus / RS485 plant rollout with autonomous-arm support.
An industrial-automation integrator ships MOS4 inside autonomous-arm gateways. Modbus RTU and RS485 ride alongside CAN; Sentry and OpenTelemetry feed the same observability stack the cloud team already runs.
Customer names, fleet sizes, and uptime numbers are kept off this page until sales explicitly clears them. Request a reference call for the full conversation under NDA.
Migration evidence
MOS 3.x → MOS 4.x: concrete before/after.
These are internal matrix figures from a real migration, not a synthetic benchmark.
- First-app-ready boot: ~90 s
- Steady-state RAM: ~60 MB
- Flash footprint: ~60 MB (jar + bin + AOT)
- First-app-ready boot: 1.6 s
- Steady-state RSS: 28.4 MB
- Flash footprint: ~30 MB release
Standards coverage
13 standards. Every one publicly specified.
| Standard | Reference |
|---|---|
| CAN Classical | ISO 11898 |
| CAN-FD | ISO 11898-1:2015 |
| ISO-TP | ISO 15765-2 |
| DoIP | ISO 13400 |
| KWP2000 / K-Line | ISO 14230 / ISO 9141 |
| UDS | ISO 14229 |
| J1939 | SAE J1939 |
| J1587 / J1708 | SAE J1587 / J1708 |
| J1850 VPW/PWM | SAE J1850 |
| ISOBUS | ISO 11783 |
| OBD-II | SAE J1979 |
| J2534 PassThru | SAE J2534 04.04 |
| FMCSA ELD | FMCSA 49 CFR Part 395 |
22 production-ready stacks (OBD-II, UDS, J1939, ISOBUS, OBFCM, Modbus, CANopen) are validated on every CI push via Python/pytest standalone tests. Source: obdstacks-v2.
Security toolchain
Verifiable from the release artefacts.
SBOM, CVE scan, licence compliance, unsafe Rust audit, static analysis. Every micro service, every commit, via the ci-gamma shared template.
| Tool | Scope | Output |
|---|---|---|
| cargo audit | CVE advisory scan | Blocking on critical advisory |
| cargo geiger | Unsafe Rust audit | Unsafe usage delta per release |
| cargo deny | OSS licence compliance | Blocking on disallowed licence |
| cargo cyclonedx | SBOM generation | CycloneDX JSON per release |
| semgrep | Static analysis | Rule-set violations blocking merge |
| pytest / distro e2e | Integration harness | 22 OBD stacks on every CI push |
Test infrastructure
Hardware-in-the-loop, not only simulation.
Integration test coverage includes hardware as well as simulation paths.
Want a reference call?
Sales mediates a 30-minute call with a customer in your vertical, under mutual NDA.