CONTEXUS platform
Smart building platform documentation
This documentation targets system integrators deploying Open IoT Hub alongside optional CONTEXUS modules. You can self-host with Docker Compose (website on localhost:9001, PostgreSQL on localhost:5433) or adapt the patterns to Kubernetes and managed Postgres.
Quickstart
Bring up docker-compose, verify health endpoints, and connect your first BACnet or MQTT device.
Architecture
How the marketing site, Open IoT Hub services, PostgreSQL, and protocol gateways fit together.
REST API
Authentication headers, error envelopes, and example requests against the IoT Hub API surface.
What you can build
CONTEXUS is a modular stack: protocol drivers ingest field data, a time-series and metadata store in PostgreSQL backs dashboards and rules, and optional analytics modules layer on top. Reference UIs live in the dashboard gallery so you can show stakeholders realistic indoor air, energy, and occupancy layouts before commissioning hardware.
Protocol coverage
Drivers and configuration guides exist for the protocols most common in commercial buildings:
- BACnet/IP for HVAC controllers and MS/TP gateways
- Modbus TCP/RTU for meters, VFDs, and packaged plant
- MQTT for modern sensors and edge publishers
- LoRaWAN for battery-powered indoor and outdoor sensors
- OPC-UA for industrial PLCs and packaged equipment
Open-source modules are described on licensing; proprietary add-ons (tenant portal, room booking, etc.) follow the partner EULA when enabled.
Operations topics
- Dashboard builder — compose widgets, bindings, and roles
- Multi-tenancy — isolate sites, integrators, and SSO realms
- Troubleshooting — FAQs, logs, and release notes stub
Next steps
Explore a running stack, review the open source repositories, estimate ROI for a deployment, or talk with the CONTEXUS team about integration and licensing.
Module licensing details are summarised on /licensing. Browse reference dashboards in the gallery.