Security and Architecture
We don't ask you to trust us blindly. Here's exactly how we isolate each client's data and authenticate every device.
Its own certificate, not a shared password
Every device gets its own signed TLS certificate the moment it's created. It connects to our MQTT broker on port 8883, always encrypted - there's never a single shared password across a fleet of devices.
Every Admin gets their own Node-RED container
When an Admin uses Node-RED to orchestrate their devices, it runs in its own isolated Docker container - not a shared instance with separate views. One Admin's flows, credentials and execution are never visible or reachable from another Admin's container.
Each Client sees only their own
A Client logs in and sees exactly their own devices and Grafana panels - nothing else from the Admin's wider portfolio. There's no shared dashboard password: every session is its own.
Continuous evaluation, not spaced-out polling
Conditions are checked every 3 seconds, per device. If a device disconnects for more than 300 seconds, its owner gets an automatic email alert.
Retention and dedicated infrastructure
Telemetry is kept at full resolution for 90 days. The time-series database, MQTT broker and Grafana all run on infrastructure dedicated to the service, with their own resource limits - they don't share compute with third-party workloads.
Account lifecycle is real
Cancelling an account doesn't leave orphaned data behind: there's a real offboarding flow with a grace period and actual purging, documented in our Terms of Service.
We're just as upfront about what we don't have yet: we don't publish a real-time uptime status page today, and we don't offer a formal contractual SLA - if that's a hard requirement for your operation, reach out via chat before deciding.