A distributed component OS for everything that moves, lifts, or sees.

Four conversations · One platform

One artefact per stakeholder.

Each pillar maps to a page the visitor can forward to the colleague who owns that decision. The CTO usually lands first; the others read what gets sent to them.

Out of the box, together

One Python container drives all four engines.

The four engines are not silos. A single Python container, talking to the in-process MQTT broker, can drive MSP, MEP, Multi Stacks, and AI Funnel from one process — no Rust toolchain, no per-engine SDK, no custom glue.

c.publish(
    "mos/msp/LoadGraph",
    json.dumps({"name": "harsh_brake", "yaml": yaml_str}),
)

c.publish(
    "mos/mep/LoadPolicy",
    json.dumps({"name": "geofence", "yaml": policy_str}),
)

c.publish(
    "mos/multi-stacks/LoadStack",
    json.dumps({"name": "j1939_truck", "json": stack_json}),
)

c.subscribe("mos/ai-runtime/detections")
c.on_message = lambda _c, _u, m: handle(m.payload)

Same MQTT client, four engines. Any MQTT-capable language — Python, Rust, C, C++, Go, JavaScript — drives the same surface. No language limit.

The pipeline

Four engines · one platform.

Every MOS4 product runs the same four-engine pipeline: bus and IoT decode, signal processing, state-machine policy, and declarative edge AI — then branches to the on-device runtime and the Munic cloud in the same OTA cycle.

flowchart LR
  Bus[CAN · CAN-FD · J1939 · Modbus] --> MS[Multi Stacks]
  Sensors[Camera · IMU · GNSS] --> MSP[MSP graphs]
  MS --> MSP
  MSP --> MEP[MEP — state-machine policy]
  MEP --> AI[AI Funnel]
  AI --> RT[On-device NPU / GPU / CPU runtime]
  AI --> Cloud[Munic cloud — OTA + retrain]
  class AI ai-node
  class RT ai-node

Cloud egress

GraphQL mesh as the customer entry point.

The end-to-end cloud path: component in container → MQTT bridge → communication gateway → cloud-connect → cloud microservice → GraphQL mesh → customer application.

flowchart LR
    A[Component in container] --> B[MQTT bridge]
    B --> C[Communication gateway]
    C --> D[cloud-connect]
    D --> E[cloud microservice]
    E --> F[GraphQL mesh]
    F --> G[Customer app]

Public GraphQL gateway reference: gateway.integration.munic.io/services/graphql_gateway/docs/

SDLC · CI · compliance

63 proto interfaces. SBOM on every release.

63 .proto files in mos-interfaces cover 46 service interfaces. cargo audit, cargo deny, cargo cyclonedx → CycloneDX SBOM. semgrep static analysis. Every micro service, every commit.