Frequently asked questions

Either. Use our managed service, or run it in your own cloud account with our support. The device and API experience is the same.

Anything that speaks MQTT over TLS (or MQTT over secure WebSocket): microcontrollers such as ESP32, Linux devices, gateways, PLC modules and cameras. LoRaWAN sensors connect through LoRaWAN gateways, and BLE devices through a BLE gateway.

Not if they use X.509 certificates. Register the existing certificates and change the endpoint and the server root CA, which most devices take as configuration. Devices on symmetric keys or tokens need a new password credential. See Moving from another IoT platform.

With an X.509 client certificate (recommended) or a username and password, always over TLS. Policies then limit what each device may connect as, publish and subscribe to.

Yes. Devices written for a shadow topic layout keep working; the twin answers them.

LoRa sensors are devices like any other in your workspace. You add each sensor with its DevEUI and AppKey and point your gateways at your workspace. Ask us for pricing for your fleet size.

Commands wait in the outbox until the device reconnects or the command expires. QoS 1 messages for a device with a persistent session are kept while it reconnects.

In the region you choose for a managed workspace, or in your own cloud account if you run it yourself.

Use Contact or the support details in your workspace welcome email. Include the device name and the time of the problem, never keys or passwords.

It depends on the number of devices and the features you use. Request a quote or sign up and we'll size it with you.