IoT platform
frequently asked questions.

Workspaces are provisioned by the service team; there is no public self-service workspace registration. Use Sign in after your account has been assigned to a workspace in the identity provider.

Sign-in is handled by Keycloak single sign-on. Your account needs an application role and a workspace assignment before you can access the dashboard. Passwords and multi-factor authentication are managed by the identity provider, not by this application.

Boards and gateways that can send HTTP JSON or connect through MQTT can integrate. Examples include ESP32, ESP8266, Wi-Fi Arduino boards, Raspberry Pi, Linux edge gateways, and cellular gateways. These are compatibility examples, not individually certified products. See the Features page for currently available transports.

HTTP and MQTT are the available device transports. TCP, UDP, CoAP, Modbus, native LoRaWAN integration, and geofencing are roadmap items. Equipment using those protocols needs a separate gateway that translates data to HTTP or MQTT; the app does not directly listen for those protocols.

A workspace admin registers the device from the dashboard. Store the generated device ID and one-time device key securely. HTTP firmware sends the key in X-Device-Key; MQTT firmware uses broker-managed credentials and a device-scoped topic ACL. Never use a human user's Keycloak access token as a firmware credential.

A networked device or gateway can send numeric latitude/longitude metrics over HTTP or MQTT. There is not yet a native map or geofence feature. LoRaWAN sensors need an external network server and a gateway that forwards normalized data; native LoRaWAN webhooks/downlinks are not implemented.

The API transports a command name and JSON payload; your firmware defines what those commands mean. Suggested examples include request_status, request_reading, and set_sampling_interval. The server does not currently enforce a command allow-list, so firmware must reject unknown commands, validate values, and enforce local safety interlocks.

The API returns whether it queued a command for MQTT or HTTP polling. That confirms delivery was queued, not that hardware acted. Firmware should acknowledge the command ID as completed or failed after handling it.

No. Do not implement shell execution or unrestricted remote code execution. Create a small, explicit command allow-list in firmware and validate payload ranges on the device itself.

The trial lasts 15 days and allows five devices. It then moves to Free, which also allows five devices and three users. Existing data is not deleted at trial expiry; adding devices beyond the Free limit is blocked.

Choose Paystack or Flutterwave v4 and a currency enabled for that provider. Paystack's documented currencies are NGN, GHS, ZAR, KES, and USD. Flutterwave currencies depend on your merchant account and configured methods. Prices convert from the NGN catalog using operator-configured rates, not live FX quotes.

Only after the server verifies the transaction reference, currency, amount, and successful status directly with the payment provider. A verified payment activates 30 days. Renewal is manual; automatic recurring billing is not enabled.

Not in this checkout. Flutterwave v4 card processing needs encrypted card collection and additional client-side handling. The current Flutterwave v4 options are configured redirect methods such as OPay, USSD, and mobile money; use Paystack for hosted card checkout.

The public Partners page describes proposed referral, certified partner, reseller wholesale, and OEM packages. Commissions, wholesale margins, support obligations, and minimum commitments require a written agreement.

Workspace name, logo, primary color, and a DNS-verified custom domain for the sign-in and workspace portal are supported. The service operator must still configure the domain's HTTPS certificate and Keycloak callback. Branded email, delegated partner hierarchy, and commission settlement are not implemented yet.

The intended offer is shared cloud operated by the service owner. Customers receive UI/API accounts, not source repository or server access. Dedicated deployments must also remain on infrastructure controlled by the service owner.