Managed MQTT/TLS · No broker to run

Connect a device.
Put it on a dashboard.

Flash an ESP32 or NodeMCU from the browser, watch telemetry arrive live, send commands, update over the air, and get alerted when a value crosses a limit.

v1/{org}/{project}/{device}/telemetry · MQTT 5 · QoS 1

₹200 welcome credit for every new account — no card needed to start
4 checkpoints broker ack → durable stream → database commit → live push
1–90 days of history kept per organization and billed by size, not by plan
27 widget types charts, gauges, switches and sliders bound to datastreams

Device library

Pick a board. Flash it from the browser.

Ready-made templates for ESP32 and ESP8266 with setup guides, pinouts and a dashboard preset. Wi-Fi details never leave your machine.

ESP8266 development board on a white surface

Live console

History you can read at a glance

Every reading stored in TimescaleDB and streamed to the console as it lands — charts, latest values and rejected messages with reasons.

Illustration of an IoT analytics dashboard with a live history chart

Alerts & commands

Act on what the board reports

Threshold, offline and no-data rules reach you by inbox, email, push or webhook. Switches and sliders send commands and wait for the report back.

Illustration of a phone receiving IoT alert notifications in a greenhouse Illustration of a phone receiving IoT alert notifications in a greenhouse

From sealed box to live dashboard in one sitting.

Choose a template, plug the board into Chrome or Edge, and the console flashes signed firmware, then hands over Wi-Fi and a fresh credential over the serial port. The Wi-Fi password is typed on your machine and never reaches our API.

Data path

Four checkpoints before a reading counts.

A message is only acknowledged when it is durable, and only shown when it is committed. Retries are deduplicated, so a board can safely send again.

  1. 01 · BROKER_ACK

    Broker-acknowledged

    The broker accepts the publish on …/telemetry and holds the ack until ingestion has it.

  2. 02 · STREAM_FSYNC

    Platform-accepted

    The envelope is validated and fsynced to a durable stream. Only then does the device get its PUBACK.

  3. 03 · DB_COMMIT

    Persisted

    One transaction stores the event, dedupes by message_id, and updates latest state and usage.

  4. 04 · LIVE_SSE

    Live

    The reading is pushed to open dashboards over SSE and evaluated against your alert rules.

Who it is for

Built for the bench, the team and the fleet.

The same pipeline serves a student’s first sensor and a white-label fleet — the difference is roles, wallets and branding, not a different product.

Makers

Build it, flash it, see it live

Students and individuals get a personal wallet and firmware that talks MQTT without running a broker, a database or a dashboard server.

Hands assembling a sensor module on a workbench

Teams

Projects, roles and shared dashboards

Operators who can command devices, developers who write credentials, project admins, and shares that view or control without editing.

Colleagues reviewing IoT dashboards on dual monitors

Enterprise

Your brand on your domain

White-label console and landing on your hostname, one enterprise wallet for every organization, and invoice billing when you need it.

Industrial control room screens showing sensor maps

The console

One console for history, devices and people.

History, device state, messages and access — the four views your team will live in.

device · history
Illustration of a device history chart Illustration of a device history chart

Pricing

Pay by the hour. No plans.

Devices, messages, history, members, projects, dashboards and alert rules — billed from a wallet. Every new account gets ₹200 of credit, and a typical device sending once a minute costs about ₹99 a month.

See pricing

Developers

Or skip the browser — publish from code.

One topic per device and one versioned JSON envelope. Any MQTT 5 or 3.1.1 client works, and the IoTAPS Arduino library wraps the contract for ESP32 and ESP8266.

mosquitto_pub -h mqtt.iotaps.com -p 8883 --capath /etc/ssl/certs \
  -V mqttv5 -q 1 -i "$DEVICE_ID" \
  -u "$CREDENTIAL_ID" -P "$SECRET" \
  -t "v1/$ORG/$PROJECT/$DEVICE/telemetry" \
  -m '{"schema_version":1,"message_id":"m-1",
       "metrics":{"temperature_c":21.5}}'

Ready when your board is

Create an account, add a device from the library, and publish your first message.

Start free