
📡 IoT
Device provisioning, telemetry pipelines, edge computing and MQTT messaging. Open any template to see the finished diagram, then use it as the starting point for your own in the Studio.
11 templates
How sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.
How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.
A general-purpose IoT platform: device connectivity, device management, data processing, rules and the apps built on top.
Where processing happens in an edge IoT setup: devices, an on-site edge server running containers, and the cloud for fleet management and long-term storage.
How a smart home reacts to events: motion, door and temperature triggers run rules for lights, locks, AC and alerts.
How MQTT messaging works between devices, a broker and applications: connect, subscribe, publish with QoS, retained messages and last will.
Every state an IoT device goes through, from manufacture to decommissioning, including updates, faults and replacement.
How a device fleet gets a firmware update safely: staged rollout, signed images, verification, reboot and automatic rollback.
The network of a smart office building: wireless sensors per floor, BACnet building systems, gateways and the building management system.
A database schema for managing an IoT fleet: devices, models, firmware versions, certificates, customers and sites.
Tracking valuable assets such as containers, tools or medical equipment with GPS and BLE tags, geofences and alerts.
More IoT templates are being added regularly.
IoT diagrams follow data from the device to the dashboard: provisioning and identity, MQTT or HTTP telemetry, the edge gateway, the cloud ingestion pipeline, storage, alerts and device updates.
They are used to plan a connected-product launch, size the ingestion pipeline and show how devices are secured and updated over the air.
Devices, the edge gateway, the MQTT broker or IoT hub, the stream processor, time-series storage, the rules engine for alerts, dashboards, and the device management service for provisioning and OTA updates.
Mark per-device certificates at provisioning, encrypted MQTT (TLS) on each connection, and a separate path for firmware updates that only signed images can use.
Yes. Open a template, then describe your own setup in the Studio, for example "smart energy meters sending readings over MQTT to AWS IoT Core with alerts on SMS", and the AI redraws the diagram with your systems.