Guides
  1. Getting Started

How Scadable Moves Your Data

Your device speaks a protocol: Modbus, BLE, Serial, GPIO, whatever it is. The Scadable binary on your gateway translates it, encrypts it with mTLS, and sends it to the cloud over MQTT. From there it's stored and queryable through the REST API, or forwarded directly to your own database. One install command. No broker setup, no certificate management, no infrastructure to maintain.

The data flow

Sensor → Gateway (Scadable binary) → MQTT (encrypted) → Scadable Cloud → Your App / Your Database

What happens at each step

At the device

Scadable speaks your sensor's protocol. You define the connection in Python:

connection = modbus_tcp(host="192.168.1.100", port=502, slave=1)
poll = every(5, SECONDS)
registers = [Register(40001, "temperature", unit="C", scale=0.1)]

The gateway polls your device on whatever interval you set. Modbus, BLE, GPIO, Serial, I2C: the protocol driver handles the translation. You just declare what to read and how often.

At the gateway

Data gets encrypted with mTLS before it leaves the device. Certificates auto-enroll on first boot and auto-rotate before they expire. You never touch them.

If connectivity drops, data buffers locally and forwards automatically when the connection returns. Nothing is lost. The binary is under 10 MB and runs on any Linux machine: Raspberry Pi, industrial PC, edge server.

In transit

MQTT over TLS. Every gateway authenticates with its own unique certificate. No shared API keys, no passwords, no bearer tokens. If a gateway is compromised, you revoke its certificate without affecting the rest of your fleet.

In the cloud

Telemetry is stored and queryable through the REST API. Every data point includes the device ID, timestamp, and field name. Query by time range, device, or field.

Audit logs track every connection, disconnection, command, and config change. When compliance asks "what happened at 3 AM on Tuesday," you have the answer.

Data forwarding

If you want data in your own database, Scadable forwards it directly. You keep your existing stack: PostgreSQL, S3, InfluxDB, whatever you already use. Scadable acts as a pass-through layer that adds encryption, certificate management, monitoring, and audit logging without changing where your data ends up.

You get the security and observability layer without migrating your data infrastructure.

What you get without building anything

These are things that normally take weeks to build. You get them the moment you install the gateway:

  • Certificate management: mTLS enrollment and rotation, no manual cert handling
  • Encrypted transport: TLS from device to cloud, every byte
  • Offline buffering: data survives connectivity drops and forwards on reconnect
  • Audit logging: every event tracked for compliance and debugging
  • Fleet monitoring: status, uptime, and health across all your gateways in one dashboard
  • Remote SSH: browser-based shell access to any gateway, no VPN or port forwarding
  • OTA updates: push new firmware to your fleet with automatic rollback on failure

Next steps

Updated about 2 hours ago