Learn

Structured learning paths for IoT system design.

Each path groups topics, guides, tools, and cases into a coherent sequence. Filter by the role you play.

Path 1

Beginner · 3–4 hours · 4 modules

IoT from Zero to One

Build a complete mental model of devices, connectivity, platforms, data, operations, and business outcomes.

Who this is for: Product managers, founders, and engineers entering IoT.
What you will learn: You can explain a complete IoT system, challenge missing layers, and frame an implementation roadmap.
Topics covered: System foundations · Device identity · MQTT · Operations

Path 2

Intermediate · 4–5 hours · 4 modules

Move from protocol basics to production topic, session, authorization, capacity, and recovery design.

Who this is for: Platform engineers, solution architects, and device teams.
What you will learn: You can design and review a production MQTT workload, including its failure behavior.
Topics covered: MQTT · Topic design · Authorization · Recovery

Path 3

Intermediate · 3–4 hours · 4 modules

Connect field protocols to edge and platform systems without erasing semantics, quality, or control boundaries.

Who this is for: Industrial engineers, gateway teams, and solution architects.
What you will learn: You can place Modbus, OPC UA, MQTT, and edge responsibilities in a coherent architecture.
Topics covered: Modbus · OPC UA · Edge gateways · MQTT

Path 4

Advanced · 5–6 hours · 4 modules

Structure identity, messaging, state, rules, data, tenancy, observability, and recovery as evolvable platform capabilities.

Who this is for: Technical leaders, platform engineers, and architects.
What you will learn: You can define platform boundaries, capacity targets, and the operating model behind them.
Topics covered: Identity · Device state · Data · Multi-tenancy

Path 5

Advanced · 4–5 hours · 4 modules

Build security across manufacturing, activation, messaging, updates, ownership changes, response, and retirement.

Who this is for: Security engineers, product owners, architects, and firmware teams.
What you will learn: You can threat-model the full device lifecycle and turn findings into enforceable controls.
Topics covered: Device identity · Authorization · OTA · Regulation

Path 6

Advanced · 3–4 hours · 4 modules

Design agents that can diagnose, recommend, and coordinate work without escaping physical-system authority boundaries.

Who this is for: AI product teams, industrial architects, operations leaders, and security reviewers.
What you will learn: You can define safe tools, approvals, evidence, fallback, and outcome verification for an IoT agent.
Topics covered: IoT agents · Authority · Digital twins · Operations