Editions: Cloud vs Community
Compare ControlBird Cloud (managed) and Community Edition (self-hosted Docker).
ControlBird comes in two editions that share the same core: the same Store, the same visual builders, the same integrations, and the same protocol services. They differ in how they are deployed, which advanced features are included, and how access is managed.
- Cloud: a managed offering with enterprise features, managed deployment, multiple environments, and single sign-on.
- Community Edition (CE): a free, self-hosted Docker image that runs a single node on your own infrastructure.
Same foundation, different packaging
Both editions are built from the same foundation, so the concepts, builders, and workflows you learn carry across either one. Cloud layers managed hosting and a set of enterprise capabilities on top of that shared core, while Community Edition gives you a self-contained node you can run anywhere.
At a Glance
| Capability | Cloud | Community Edition |
|---|---|---|
| Deployment | Managed hosting | Self-hosted Docker container |
| Price | Subscription | Free |
| Container image | Managed (no image to run) | ghcr.io/controlbird/platform-ce:latest (public) |
| Authentication | Single sign-on (SSO) | Local credentials |
| Node management | Multiple environments and nodes via the cloud control plane | A single self-contained node |
| Core builders & integrations | Yes | Yes |
| Protocols: Modbus, MQTT, HTTP, CoAP, OPC UA, SMTP | Yes | Yes |
| Industrial protocols: BACnet, DNP3, EtherNet/IP | Yes | No |
| Historian | Yes | No |
| Smart Assistant | Yes | No |
| White labeling | Yes | No |
Running Each Edition
Cloud
Cloud users sign in with single sign-on and work through the cloud control plane to manage instances, environments, nodes, users, and licenses. From there you can deploy nodes, run multiple environments side by side, and enable secure tunnel access for nodes that live on a local network. See the configure walkthrough and the certificates guide for setup details.
Community Edition
Community Edition runs as a single Docker container. Mount a data directory for persistence and expose the kernel port:
docker run -p 9100:9100 \
-v /path/to/data:/opt/controlbird/data \
ghcr.io/controlbird/platform-ce:latestOnce the container is running, open the local web UI and sign in with local credentials. The dedicated CE walkthrough covers this in three steps: install Docker, run the container, and access the UI.
Edition-aware walkthroughs
The getting-started walkthrough adapts to your edition. The Cloud path has four setup steps (sign up, create an environment, deploy a node, access it); the CE path has three (install Docker, run the container, access the UI). After setup, both editions share the same steps: architecture, exploring the platform, adding devices, building schematics, and creating automations.
What's Included Where
Community Edition is a complete, free way to run ControlBird on a single self-hosted node. It includes the Store, the visual builders, and the core protocol services (Modbus, MQTT, HTTP, CoAP, OPC UA, and SMTP), so you can model devices, build schematics, and create automations end to end.
Cloud adds capabilities aimed at larger and team deployments:
- Managed hosting with multiple environments and nodes.
- Centralized management through the cloud control plane.
- Enterprise single sign-on.
- The built-in historian for time-series data retention.
- Industrial protocols: BACnet, DNP3, and EtherNet/IP.
- The Smart Assistant.
- White labeling.
When you outgrow a single self-hosted node, the same models and workflows carry forward, so moving to Cloud is a matter of changing where ControlBird runs rather than relearning the product.
For a deeper look at the entity tree these editions configure, see Data Model, and for how the Store and services fit together, see Architecture Overview.