CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/IoT

πŸ“‘ IoT Β· Deployment Β· Pro

IoT Edge Computing Deployment

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.

More IoT templates

Deployment diagrams are part of Pro. Anyone can view this one; generating and editing it needs Pro.

Drawing diagram…

What this diagram shows

  • Edge server filters and analyses data locally
  • Site keeps working during internet outages
  • Cloud deploys container updates to all edge sites

Prompt used

Deployment for IoT edge computing: cameras and sensors on a site connect to an edge server running K3s with containers for data filtering, local ML inference (defect detection), a local time-series buffer and a local dashboard. The edge syncs summarised data to the cloud over 4G/fibre and keeps buffering during outages. The cloud hosts the fleet manager that deploys container updates, the data lake and central dashboards.

Mermaid code
flowchart TB
  subgraph Site[Factory / Store Site]
    CAM[Cameras]
    SEN[Sensors]
    subgraph Edge[Edge Server - K3s]
      FIL[Data Filter]
      INF[ML Inference - defect detection]
      BUF[(Local Buffer)]
      LDASH[Local Dashboard]
    end
  end
  subgraph Cloud[Cloud]
    FLEET[Fleet Manager]
    LAKE[(Data Lake)]
    CDASH[Central Dashboards]
  end
  CAM -->|"RTSP video"| INF
  SEN -->|"MQTT readings"| FIL
  FIL -->|"Filtered readings"| BUF
  INF -->|"Defect results"| BUF
  BUF -->|"Local metrics"| LDASH
  BUF -->|Summaries over 4G / fibre| LAKE
  LAKE -->|"Site analytics"| CDASH
  FLEET -->|Container updates| Edge

Inside this diagram

A deployment diagram with 10 components in 3 environments and 8 connections.

Environments and what runs in them

  • Factory / Store Site: Cameras and Sensors
  • Edge Server - K3s: Data Filter, ML Inference - defect detection, Local Buffer and Local Dashboard
  • Cloud: Fleet Manager, Data Lake and Central Dashboards

Outside these environments

  • Edge

Data stores

  • Local Buffer
  • Data Lake

Connections

  • Cameras β†’ ML Inference - defect detection: RTSP video
  • Sensors β†’ Data Filter: MQTT readings
  • Data Filter β†’ Local Buffer: Filtered readings
  • ML Inference - defect detection β†’ Local Buffer: Defect results
  • Local Buffer β†’ Local Dashboard: Local metrics
  • Local Buffer β†’ Data Lake: Summaries over 4G / fibre
  • Data Lake β†’ Central Dashboards: Site analytics
  • Fleet Manager β†’ Edge: Container updates

Make your own diagram like this

Describe your own system in plain English and the AI cloud architecture diagram generator draws it in seconds, in the same style as this template.

Related templates

Data FlowIoT

IoT Telemetry Data Pipeline

How sensor readings travel from devices to dashboards and alerts: MQTT ingestion, stream processing, time-series storage and anomaly detection.

SequenceIoT

IoT Device Provisioning Sequence

How a new device joins the platform securely: claiming by the owner, certificate issue and its first connection to the MQTT broker.

C4 ArchitectureProIoT

IoT Platform Reference Architecture

A general-purpose IoT platform: device connectivity, device management, data processing, rules and the apps built on top.

FlowchartIoT

Smart Home Automation Flow

How a smart home reacts to events: motion, door and temperature triggers run rules for lights, locks, AC and alerts.

SequenceIoT

MQTT Publish/Subscribe Messaging

How MQTT messaging works between devices, a broker and applications: connect, subscribe, publish with QoS, retained messages and last will.

State MachineIoT

IoT Device Lifecycle

Every state an IoT device goes through, from manufacture to decommissioning, including updates, faults and replacement.