Tiers / products
Choose your CitusIO tier.
What happens if a node restarts? Which devices and systems must connect? Who may change the deployment?
Every tier permits real production use. Free provides a memory-backed live MQTT node. Paid plans add the selected capabilities, artifact access, updates and service commitments.
Free
Teams whose live data can be regenerated from devices. Run MQTT, inspect live state and deliver selected events to a webhook or your own adapter.
Memory-backed state
Pro
Teams responsible for recovering device messages after a restart. Persist broker and delivery state in PostgreSQL, with TLS, secure WebSocket and standard support.
Production node
Max
Teams connecting plant devices and telemetry to business systems. Validate and transform messages, acquire industrial data and send bounded delivery work to configured sinks.
Production node
Enterprise
Operations teams managing failover, identity and audited changes. Operate an active–standby pair with external fencing, verified roles, audit and governed command workflows.
Active–standby pair
Which boundary affects your application?
| Tier | Plan for this requirement | Next step |
|---|---|---|
| Free | Memory-backed state is lost on restart. Plan application replay where readings matter. | container-setup |
| Pro | Provide PostgreSQL, its trust and credentials, and verified backups. This tier runs a single active broker node. | durable-recovery |
| Max | Each gateway and sink has a declared protocol/profile. Validate the selected provider and failure behavior. | integration-bridges |
| Enterprise | Supply the identity edge, external fencing/router and PostgreSQL. Promotion requires proven writer ownership and replay. | enterprise-operations |
All tiers contain the panel, API operating contracts and public C Bridge SDK. The installed backend and verified identity determine available views and commands.