Product overview

The IoT platform that ships with you

Autoconnecto is multi-tenant SaaS for connecting devices, processing payloads with optional pipelines, building live dashboards, and controlling equipment — with dashboards that stay correct after every reboot.

Built in India · INR pricing · No ThingsBoard-style rule-engine maze on day one

60+
Dashboard widgets
14+
Pipeline step types
2
Pipeline kinds
99.9%
Uptime target

From device to decision

One coherent path — not a bag of disconnected microservices you stitch together.

STEP 1
Connect
MQTT, HTTPS, WebSocket, gateways, LoRa webhooks
STEP 2
Process
Optional data & attribute pipelines per device profile
STEP 3
Store
Telemetry, attributes, alarms — tenant-isolated Postgres
STEP 4
Visualize
Live dashboards, 60+ widgets, mobile app
STEP 5
Act
Alarms, shared attributes, remote control

Everything in one platform

Pick what you need. Leave pipelines blank and behavior stays exactly as today — raw ingest, no forced configuration.

Universal connectivity

ESP32 SDK, REST/MQTT ingest, device WebSocket, gateway child relay, ChirpStack & generic webhooks.

MQTT TLSHTTPSWebSocketLoRa

Live dashboards

Drag-and-drop builder, realtime Socket.IO, 60+ widget types — charts, maps, gauges, tables, controls.

60+ widgetsRealtimeShare & embed

Data pipelines

Transform telemetry before storage: rename, filter, scale, flatten, compute fields, webhooks — bound per device profile.

Per profilePreviewFail-open

Attribute pipelines

Same step engine on client attribute patches — bulk key scope changes, defaults, coercion, conditional drop.

Patch mergeScope renameOptional

Alarms & rules

Profile alarm rules on telemetry and attributes. Escalation, acknowledge, inactivity — without a heavy rule-engine canvas.

ThresholdsInactivityNotify

Enterprise ready

Multi-tenant isolation, RBAC, white-label branding, custom domains, INR plans from free tier to enterprise.

RBACWhite-labelMulti-tenant
Processing layer

Data pipelines & attribute pipelines

Two separate pipeline types, one step engine. Bind each optionally on a device profile — not per device, not tenant-wide. Blank binding means passthrough: store payloads as received.

Data pipelines (telemetry)

Run on every telemetry message before database write, realtime emit, and alarm evaluation.

Rename keysChange scopeFilter / clampScale & deriveFlatten JSONPick keysWebhook

Attribute pipelines (client attributes)

Run on each client attribute patch before merge into stored state — ideal for normalizing config keys from firmware.

Change scopeSet defaultsCoerce typesCopy keyConditional dropRemove empty
Telemetry example — rename + pick keys
Device sends
{
  "T1": 24.2,
  "humidity": 61,
  "extra_debug": true
}
Stored & live UI
{
  "temperature": 24.2,
  "humidity": 61
}
Attribute example — change scope (prefix)
Device sends
{
  "cfg.tempMin": 18,
  "cfg.mode": "auto"
}
Stored & live UI
{
  "config.tempMin": 18,
  "config.mode": "auto"
}
  • Preview in UI
    Sample JSON in → transformed out, with warnings
  • Fail-open
    Pipeline errors never block ingest
  • Kill switches
    Disable via env without redeploying old code
Differentiator

Reboot-safe remote control

Operator dashboards often lie after a device reboot — toggles show the wrong state until someone clicks again. Autoconnecto ties shared attributes, client confirmation, and UI resync into one flow.

Read how it works in docs
  1. 1

    Operator sets a value on the dashboard (shared attribute).

  2. 2

    Device applies it and confirms via client attribute.

  3. 3

    After reboot, device reloads retained shared attributes and re-confirms.

  4. 4

    Dashboard resynchronizes — no duplicate clicks.

Who it's for

Industrial IoT OEMsSystem integratorsEnergy & utilitiesSmart buildingsFleet & logisticsProduct engineering teams

Ready to connect your fleet?

Start on the free tier, bind a pipeline when you need it, and scale to white-label enterprise when you're production-ready.