Always on. Both directions.
Every device connects the moment it powers on, and stays connected — no polling, no waiting for the next check-in. The same connection carries sensor data up and commands back down, so your fleet is never just reporting in.
How a device joins your fleet
Your device reaches out
Connects the moment it powers on, using the same lightweight protocol most IoT hardware already ships with — nothing new to build into your firmware.
The platform checks it
Every device proves who it is on its own — never a shared password sitting on your hardware.
It's online
Connected and ready, whether it's your first device or your ten-thousandth.
What an always-on link gives you
No polling, no delay
Readings and state changes arrive the instant they happen, not on the next scheduled check-in.
The platform notices if it drops
A device that goes quiet is flagged within moments — not the next time someone happens to look.
Picks back up on its own
A dropped connection reconnects automatically — nothing for your team to step in and fix.
Data up, commands down — the same connection
Sends
Sensor readings and reported state flow up continuously, the moment they change.
Receives
Commands from an automation or your team travel back down that exact same connection.
Confirms
Every command is acknowledged, so you know it actually landed — not just that it went out.
The connection is the easy part.
Nothing about getting connected should be the hard part of shipping your product.
Works with what you're already building
MQTT 3.1 and 3.1.1 — the versions almost every IoT chipset and firmware stack already speaks — with QoS 0, 1, and 2, so your devices choose exactly how strict delivery needs to be.
Nothing for you to run
Nothing to install, patch, or keep online yourself — every device connects straight to the platform.
Ten devices or ten thousand
Connecting doesn't get any harder as your fleet grows — capacity scales with you automatically.
Every device, its own signed identity
Each device connects with its own signed credential, never a shared password — scoped to that exact device and account, and it can't outlive its welcome even if it tried.
- Protocol — MQTT 3.1 and 3.1.1.
- Delivery — QoS 0, 1, or 2 for whatever your devices send up. Commands the platform sends back down always go at QoS 1 and are held for a short window if a device is briefly offline, so a momentary drop doesn't cost you the command.
- Authentication — every device presents a signed token on connect, verified against a key that belongs to that device alone. It's checked against the exact account and device it was issued for, capped at 24 hours before it needs renewing, and rotates without any downtime on your end.
Low-power, wide-area connectivity for battery-run and remote hardware is next on the roadmap.