Resources · Docs
Where the reference lives.
89 protobuf files define every MOS4 inter-service contract. Reference documentation is in early access — coverage expanding. All developer portal entry points are available to registered partners.
Interface surface
89 proto files. One typed registry.
The mos-interfaces repo is the single shared registry for all MOS4
service contracts. Every service talks to every other via these wire contracts — proto3 with
buf lint and cargo build
enforced on every merge. Backward compatibility is a CI gate, not a convention.
Rust crate documentation (Rustdoc) and protobuf interface documentation (buf schema) are the two primary developer-facing reference formats.
Service domains
Services across six domains.
| Domain | Services | Count |
|---|---|---|
| Connectivity | modem, eUICC, routing, BT, WiFi, DHCP, MQTT, MEP, RPC bridge, binarygate | 10 |
| Positioning | GNSS, GNSS-ESF | 2 |
| Vision | camera capture, dashcam, frame plane, ROI shader, inference runtime, VSLAM | 7 |
| Power | power manager, energy referee, battery, peripheral power | 4 |
| Data | database, database admin, SQL, PDM, sensors, 1-wire, Modbus, USB, geofencing, I/O, interactive mode, MSP, OBD | 13 |
| Platform | logs, sentry, monitoring, observability reporter, time manager, version, watchdog | 7 |
Go bindings are generated alongside Rust stubs — any non-Rust consumer can use the same proto contracts.
Getting started
Developer portal entry points.
Coming to the developer portal
SDK quickstart
A step-by-step getting-started guide covering SDK setup, container tooling, and first micro service deployment is being prepared for the developer documentation portal. This card will link directly to it once the URL is confirmed.
Available to registered partners — request early access via engineering.
Developer portal · early access
SDK reference
Crate-by-crate Rust documentation — interfaces, configuration schemas, and examples. Available to registered partners on the developer documentation portal.
Reference documentation is in early access — coverage expanding.
Developer portal · early access
Protobuf interface reference
Public proto3 interface definitions for every MOS4 service — the canonical wire-contract reference for any language consuming MOS4 services.
Available to registered partners via the developer documentation portal.
Developer portal · early access
AI inference TOML reference
Schema, examples, and supported model types for on-device AI inference pipeline configuration — covers the funnel DAG model, triage triggers, and per-class inference settings.
Available to registered partners via the developer documentation portal.
Developer portal · early access
Multi Stacks rule reference
YAML grammar for vehicle and machine protocol decoders — covers the declarative stack DSL, protocol selectors, and multi-bus concurrency model.
Available to registered partners via the developer documentation portal.
Documentation corpus
The documentation we maintain.
| Corpus | Count | Maturity |
|---|---|---|
| micro service dossiers | 52 | published |
| Core repo dossiers | 7 | published |
| Tool repo dossiers | 9 | published |
Per-component reference documentation — one-liner, provided/required interfaces, key concepts, and integration touchpoints — is being prepared for publication on the developer documentation portal after content review. No timeline is committed.
GraphQL mesh
Cloud egress entry point.
GraphQL mesh — cloud API gateway
The cloud user entry point is the GraphQL mesh. End-to-end flow: component-in-container → MQTT broker → communication gateway → internet → cloud-connect → cloud micro service → GraphQL mesh → customer API. The mesh consolidates all MOS4 cloud service contracts behind a single typed query surface.
Public reference: gateway.munic.io → GraphQL gateway docs →
Developer tools
Host-side tools for development and QA.
-
MSP graph editor
Web-based signal-processing graph editor with a curated kernel registry. Off-target development and testing — no hardware required.
-
mos-log-reader
Host-side CLI for parsing, merging, colorizing, and interactively exploring MOS4 device log streams.
-
mos-mes — ECU simulator
Rust ECU simulator for CAN/ISO-TP/UDS/OBD-II/DoIP protocol testing, headless or via web dashboard. Hardware-free integration testing for diagnostics stacks.
Ready to start integrating?
Request access to the developer documentation portal or talk to engineering about your program.