iot-dc3
IoT DC3 — Connect the Physical World to AI. An open-source Industrial IoT Runtime for Physical AI: 36 protocol drivers, edge-to-cloud data delivery, and an MCP
What is iot-dc3?
IoT DC3 — Connect the Physical World to AI. An open-source Industrial IoT Runtime for Physical AI: 36 protocol drivers, edge-to-cloud data delivery, and an MCP tool gateway so AI agents act on devices in a safe, controllable, traceable loop.
Overview of iot-dc3
What it is
IoT DC3 — Connect the Physical World to AI. It is an open-source Industrial IoT Runtime for Physical AI. It provides 36 protocol drivers for device connectivity, edge-to-cloud data delivery, and an MCP tool gateway so AI agents can act on devices in a safe, controllable, traceable loop. The project is hosted at https://github.com/pnoker/iot-dc3 and its homepage is https://dc3.site. IoT DC3 decouples devices from applications: drivers push normalized point data into a message bus, and applications consume it through one unified API — add or change devices without touching applications, and build new applications without touching devices.
Key features
- Multi-protocol device connectivity: 36 access driver modules covering industrial protocols (Modbus TCP/RTU, OPC UA/DA, Siemens S7, BACnet/IP, etc.), IoT protocols (MQTT, CoAP, LwM2M, BLE, etc.), data bridging (MySQL, PostgreSQL, Oracle, etc.), basic communication (TCP/UDP, Serial, SNMP), and simulation/debugging. A Driver SDK supports custom protocol driver development.
- MCP tool gateway for Physical AI: Built on Spring AI, the Agentic Center exposes an MCP tool gateway for external AI agents, with OAuth client registration, per-tool authorization, and full audit trails. Supports natural-language device queries, read/write points, intelligent alarm analysis, data insights, and multi-model providers (GPT, Claude, DeepSeek, Qwen).
- Cloud-native microservices: Based on Spring Boot 4 + Spring Cloud 2025 with gRPC service calls, Spring Cloud Gateway, stateless design for horizontal scaling, and fault isolation.
- Real-time data engine: Drivers send telemetry asynchronously through an internal pluggable message broker (RabbitMQ default, Kafka, Pulsar, or MQTT 5). Includes time-series storage, a rule engine for multi-level alarms, and full event traceability.
- Enterprise security and multi-tenancy: Tenant isolation across database, cache, and API paths; JWT + Spring Security RBAC; TLS/SSL support; audit tracking.
- Developer friendly: Separated Vue 3 + TypeScript frontend, RESTful/gRPC APIs, containerized deployment with Podman/Docker Compose, Docker Swarm, Kubernetes, and Helm configs. Complete online documentation.
Use cases
IoT DC3 is suitable for connecting industrial devices (PLCs, sensors, RTUs) via standard protocols to a centralized platform, enabling AI-driven monitoring, natural-language device management, intelligent alarm analysis, and data insights. It can be used in smart manufacturing, energy management, building automation, and other industrial IoT scenarios where device-data decoupling and multi-tenancy are required.
Getting started
To start local development, first start PostgreSQL and RabbitMQ, load environment variables, then build: bash make up-db source dc3/env/dev.env.sh mvn -s .mvn/settings.xml clean package For users in Mainland China, replace make up-db with make up-db-cn to use the Alibaba Cloud registry. For full instructions, see the repository Quickstart guide.
License and pricing
The license is not stated in the provided metadata. The project is listed as open source (pricing_type: open_source).
Based on the project's public README and repository metadata.