Comparison
OpenRemote vs CONTEXUS
OpenRemote targets IoT asset management and rules. CONTEXUS targets modular smart building delivery for integrators. Confirm licence and connector lists on each vendor's official repository before contract.
| Dimension | OpenRemote | CONTEXUS |
|---|---|---|
| Protocols | MQTT, HTTP, KNX, and protocol agents via OpenRemote manager; building buses depend on configured agents. | MQTT, LoRaWAN, BACnet, Modbus, OPC-UA in CONTEXUS docs; integrators assemble protocol coverage per site. |
| Licensing | OpenRemote 3.x manager is published under AGPL-3.0 (verify repository licence before redistribution). | Open source modules; partner licensing for white-label and commercial support tiers. |
| White-label | Custom domains and branding possible on self-hosted stacks; partner programmes vary by region. | Certified and Premier partner tiers include formal white-label rights for integrators. |
| Self-host | Docker-based manager deployments on customer infrastructure are supported. | Self-host via documented Docker and Node stack; suitable for air-gapped or sovereign cloud policies. |
| Digital twin | Asset attributes, geolocation, rules, and dashboards for equipment-centric twins. | Building-centric twins with floor plans, 7D BIM linkage, and portfolio modules (energy, analytics). |
Next steps with CONTEXUS
Explore modules, deployment options, licensing, or talk to our team about your building portfolio.