Appearance
What is Autoconnecto?
Autoconnecto is a production-grade IoT platform as a service operated from India. Teams use it to connect field devices, stream real-time telemetry, build operational dashboards, raise alarms, run rule chains, and remotely control equipment—without building and operating a custom MQTT broker, time-series database, and web UI stack.
- Product URL: https://app.autoconnecto.in
- API URL: https://api.autoconnecto.in
- Documentation: https://docs.autoconnecto.in
What problem Autoconnecto solves
Industrial and product teams need three things at once:
- Visibility — what each device is doing now and historically.
- Control — change setpoints, switches, and limits from a dashboard or API.
- Trust — after a power outage or reboot, the dashboard must reflect real hardware state, not the last command someone clicked hours ago.
Many IoT stacks deliver charts but leave control UIs stale after reboot. Autoconnecto is designed around an attribute feedback loop so operators see confirmed device state, not assumed state.
How Autoconnecto works (high level)
Devices (ESP32, gateways, integrations)
↓ MQTT (WSS) / HTTP / WebSocket / webhooks
Autoconnecto cloud (ingest, storage, rules, alarms)
↓ real-time events
Browsers & mobile app (dashboards, operators)Inbound from devices: telemetry, client attributes (confirmed state), RPC responses.
Outbound to devices: shared attributes (desired state, retained), RPC commands, command publish over MQTT or device WebSocket.
To operators: live Socket.IO updates on dashboards; historical telemetry queries; alarm workflows.
Primary differentiator: attribute feedback after reboot
Autoconnecto uses shared attributes for persistent desired state (e.g. relay on/off, slider setpoint) and client attributes for what the device confirms it applied.
Typical control flow:
- Operator changes a control widget on the dashboard.
- Platform persists a shared attribute and publishes it to the device (MQTT retained).
- Device applies the value to hardware and publishes a matching client attribute.
- Dashboard receives the client attribute and shows confirmed state.
After power cycle: the device requests shared attributes at startup, reapplies them, and sends client confirmations. The dashboard resynchronizes without manual re-command—a common pain point on other IoT platforms.
Stateful controls (switches, sliders, attribute cards) use this model. One-shot actions (reboot, trigger) use RPC instead.
Platform capabilities
| Area | Capabilities |
|---|---|
| Connectivity | MQTT over WSS; device WebSocket; HTTP telemetry and batch; integration webhooks (e.g. ChirpStack / LoRa) |
| Devices | Lifecycle management, bulk import, device types and profiles |
| Data | Time-series telemetry with plan-based retention and rate limits |
| Visualization | Dashboards with a large widget library (gauges, charts, maps, tables, controls, alarms) |
| Operations | Alarms, acknowledgements, rule chains, assets, Solutions (dashboard templates) |
| SaaS | Multi-tenant isolation, user roles, tenant branding (white-label on eligible plans) |
| Developers | REST API, OpenAPI/Swagger in-app; ESP32 SDK |
Who Autoconnecto is for
- Industrial IoT — pumps, generators, PLCs, environmental monitoring
- Energy & utilities — distributed assets, thresholds, compliance views
- Logistics & field assets — health, utilisation, location-aware dashboards
- OEMs & integrators — white-label IoT under a customer brand
- Product teams — ship connected devices faster with dashboards and SDK already integrated
Geography: global connectivity; INR pricing and India-based support contact for commercial customers.
Pricing
Transparent INR tiers from Free through Enterprise. See Pricing.
Enterprise volume, custom limits, and SLAs: founder@autoconnecto.in · +91 92121 00555.
Contact
| Purpose | |
|---|---|
| Support | support@autoconnecto.in |
| Enterprise & partnerships | founder@autoconnecto.in |
| Phone | +91 92121 00555 |