Device feature

Managed MQTT for connected hardware. No broker setup.

Skip broker provisioning, certificates, and topic-tree design. Publish and subscribe in three steps.

MQTT broker for ESP32managed MQTT IoTMQTT vs HTTP for IoTMQTT hosting

Why managed MQTT

MQTT is the right protocol for connected devices. Pub/sub, low overhead, designed for unreliable networks. Standing up your own broker is the wrong way to spend a quarter. AWS IoT works, but its setup ladder (thing types, policies, certificates, topic rules, IAM) is a 50-step affair before your first message lands.

SCADABLE runs the broker for you. Your devices talk to a regional endpoint over TLS, your console subscribes from the browser, and topic structure is provisioned per organization.

Three lines instead of fifty steps

#include "scadable.h"

scadable_init(NULL);                                          // pulls device cert from NVS
scadable_connect();                                           // mTLS broker handshake
scadable_publish(SCADABLE_CH_TEMP, "23.4", 4, /*qos=*/1);     // batched, retried, TLS
scadable_on_event(on_event_cb, NULL);                         // inbound + lifecycle events

AWS IoT vs SCADABLE

AWS IoT: thing types, policies, certificates, topic rules, IAM, billing alarms, dashboards built in Grafana
SCADABLE: one SDK call. Console shows the topic tree live. Done.
Both run on the same standard MQTT 3.1.1 / 5.0 protocol. Your existing tooling works.

What we handle

TLS 1.3 termination with per-device X.509 certificates
Automatic reconnection with backoff on network changes
QoS 0/1/2 with persistent sessions and last-will messages
Topic-level access control, scoped per device and per namespace

Bring your fleet onto SCADABLE.

Connect a repo, leave with a fleet you can manage from your codebase.

Let’s talk