IoT Gateway

Reference architecture for a connected-device platform: edge devices, gateways, ingestion, processing and dashboards.

This example project demonstrates the IOModel approach to Architecture as Code by expressing a complete reference architecture as a tree of YAML files alongside MDX documentation. Open the Explore tab to navigate the model interactively.

What you will find here

• Architecture — full system context, data architecture, integrations, deployment, quality attributes, plus the Actors and Modules reference pages.
• Workflows — main end-to-end flows that exercise multiple systems.
• Scenarios — concrete edge cases used as design and test references.

Top-level systems

• Edge — Code that runs on the device or local gateway.
• Ingestion — Cloud-side ingestion of device telemetry and commands.
• Stream Processing — Real-time and batch processing of telemetry.
• Device Management — Inventory, configuration and OTA for the device fleet.
• User-Facing Apps — Web and mobile apps for owners and operators.
• Platform — Shared platform services: secrets, observability, deploy.

How the model is structured

The model uses three nesting layers:

1. Top layer — systems / subsystems / domains and actors of the product. Cross-system links describe high-level integrations.
2. Container layer — each system decomposes into service-containers (services, apps, libraries). Containers can link to other containers across systems.
3. Component layer — each container holds components (libraries, internal modules). Component links are internal-only and never cross container boundaries.