The IoT platform that ships with you
Connect a device. The reading is stored. A profile alarm and a rule engine can both act. Analytics answers from those readings. The dashboard shows the last value the device reported.
Built in India · INR plans · Hosted multi-node · Scaled when you need more
From device to decision
One coherent path — not a bag of disconnected microservices you stitch together.
Everything in one platform
Pick what you need. Skip the Rule Engine and behavior stays simple — raw ingest plus profile Alarm Rules when you add them.
Universal connectivity
ESP32 SDK over MQTT, HTTPS, the device WebSocket, gateway child relay, and LoRaWAN webhooks. MQTT over WebSocket is port 8084. OPC UA, BACnet, and Sparkplug are gateway protocols.
Live dashboards
Drag-and-drop builder, realtime Socket.IO, 80+ widget types — charts, maps, gauges, tables, controls.
Visual Rule Engine
Graph automation on ingest: filter, transform, notify (Telegram/email), webhooks, attributes, commands, LoRa downlink — bound per device profile or tenant default.
Alarms & notifications
Profile Alarm Rules plus Rule Engine create_alarm. Escalation, acknowledge, inactivity, email digests, and Telegram L1/L2/L3 ops groups for the plant team.
Analytics with AI
Ask in ordinary words. Analytics ranks a fleet, forecasts a crossing, checks vibration, and can learn a normal band. The number comes from stored telemetry.
Hosted multi-node
App and API on one node, Timescale on a dedicated database node. One logical database, tenant-scoped. Roles inside the tenant. White-label logo, colours, and your hostname on Growth and Enterprise. Plans list up to 500 devices on Enterprise. If you need more, it can be scaled.
Visual Rule Engine
One graph on the ingest path — transform, branch, notify, forward, and control. Bind a Started engine on the device profile (or a tenant default). Simple thresholds stay on profile Alarm Rules.
- Dry-run previewSample JSON in → path highlight on the canvas
- Fail-openUnexpected errors never block ingest unless you drop
- Telegram ops groupOne group chat id for tenant-wide alarm posts
Reboot-safe remote control
The dashboard writes a shared attribute. The device applies it and reports a client attribute. The widget shows the last value the device reported. An offline device does not show the command as done. After power returns, the device reads the shared attribute again.
Read how it works in docs- 1
The dashboard writes a shared attribute.
- 2
The device applies it and reports a client attribute.
- 3
The widget shows that report. Offline does not mean the command is done.
- 4
After power returns, the device reads the shared attribute again.
Who it's for
Ready to connect your fleet?
Start on the Free plan. White-label is on Growth and Enterprise. If you need more than the catalog, it can be scaled.