The IoT Cube platform

The technology layer beneath connected products.

IoT Cube sits between the physical world and the software that runs your business. Devices connect through one ingestion layer, telemetry is joined to the asset record, rules turn it into action, and your own applications read all of it through open APIs.

Request a Demo

Tell us about your operation. A specialist will get back to you to arrange a demo.

Explore the modules
Hosting
In-Kingdom, private cloud or on-site
Neutral on
Devices, carriers and AI models
Running on it
Twelve products today

One reading, end to end

1.4s
  1. 02:14:00A reading arrivesReefer sensor on trailer TR-208, over MQTT
  2. 02:14:00It finds its recordTrailer, shipment, customer and contract
  3. 02:14:01A rule recognises itAbove 8 °C for longer than ten minutes
  4. 02:14:01Someone is toldDepot supervisor on shift, not a shared inbox
  5. 02:14:01Your systems knowWebhook to the customer's own platform

Illustrative trace, not a customer record

/ How it fits together /

Five layers, running as one platform.

A reading enters at the bottom and leaves as something your business can act on. Each layer can be taken on its own, and all five share one asset record.

01

Connect

Every device, machine and system you already run. Whatever brand, whatever protocol, whatever carrier.

02

Manage

Control, configuration, identity and access at scale. Devices are treated as a lifecycle, not a list.

03

Context

A signal becomes a fact when it sits next to your business data.

04

Automate

Events become workflows, alerts and actions. The response no longer depends on who happened to be watching.

05

Build

Build applications, dashboards and products on top. The twelfth use case costs a fraction of the first.

/ What you can do with it /

Pick a job. See what ships with it.

The same five layers, indexed by the thing you are trying to get done rather than by where it sits in the stack.

01 / Get data inConnect layer

Bring in the estate you already own.

Trackers, meters, sensors, PLCs and gateways arrive through one ingestion layer. Nothing is replaced to get started, and nothing is locked to a single supplier later.

  • Protocol adaptersMQTT, HTTP, LwM2M, CoAP, Modbus and OPC UA handled at the edge of the platform, not in custom code.
  • Device registryEvery device has an identity, an owner, a configuration and a history, searchable across brands.
  • Over-the-air updatesPush firmware and configuration to supported devices in controlled, reversible batches.
  • Edge bufferingWhere the network drops, data queues locally and backfills in order when it returns.

/ Specifications /

The technical detail your architects will ask for.

Supported protocols, networks and integrations. Ask us to prove any of it against your own hardware.

iotcube · platform — specifications

read only

iotcube@platform:~$ spec --show device-protocols

  • MQTT 3.1.1 / 5
  • HTTP(S) & REST
  • LwM2M / CoAP
  • Modbus RTU & TCP
  • OPC UA
  • CAN / J1939 via gateway
  • DLMS/COSEM via head-end

iotcube@platform:~$

33 supported capabilities across 6 groups. Ask us to prove any line against your own hardware.

/ Deployment /

Runs where your policy says it must.

Four ways to deploy. One product, the same APIs and the same upgrade path in each.

Option 1 of 4Most common

Sovereign cloud

Hosted and operated by IoT Cube inside the Kingdom.

  • Fastest start
  • Data resident in Saudi Arabia
  • Managed upgrades

/ Intelligence /

Bring your own model.

The platform is AI neutral. Pick a case below to see what a model is given, what it concludes, and where that conclusion has to land for anyone to care.

In

What the model sees

Live temperature, door events and position from a reefer trailer, joined to the shipment and the route it is running.

  • Telemetry
  • Asset record
  • Route history
Model

What it concludes

This cooling curve does not match the last few hundred trips on this lane, and the gap is widening.

Out

Where it lands

An alert to the depot supervisor on shift, with the trip and the readings attached, while the load can still be saved.

  • Alert
  • Named owner
  • Evidence attached

Illustrative examples. The model is yours: hosted by you, by us, or called as an API. What the platform supplies is the record it reasons over and somewhere for its answer to land.

/ Developers /

Open at the top. No black boxes.

Publish telemetry, read assets and react to events with the tools your team already knows.

  • REST APIs and webhooks

    Read assets, publish telemetry, subscribe to events.

  • Streaming export

    Push the raw stream into your own data platform.

  • White-label portals

    Your brand on the portal and the mobile app.

  • Sandbox tenants

    An isolated tenant for partners to build against.

iotcube · api — Send telemetry · MQTT

Illustrative
# Publish a reading from any device or gateway
topic   tenants/acme/assets/TR-208/telemetry
payload {
  "ts": "2026-09-13T02:14:00+03:00",
  "temperature_c": 5.4,
  "door": "closed",
  "location": { "lat": 26.4207, "lon": 50.0888 }
}

/ Security & sovereignty /

Where your data lives, and who can reach it.

In-Kingdom residency

Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.

Built to national controls

Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.

Isolated by tenant

Tenant isolation, role-based access and a full audit trail across users, actions and devices.

Your cloud or site

Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.

Read the data residency statement

/ Ecosystem /

Twelve products already stand on it.

The same APIs, multi-tenancy and white-label options behind these products are open to your own team.

/ Questions /

Frequently asked.

No. Device neutrality is the design principle. We connect the trackers, meters and sensors you already own, and prove it with your hardware early in a demo.

Walk through the architecture with our engineers.

Bring your device list, your protocols and your hosting policy, and we will map them onto the five layers.

Request a Demo

Tell us about your operation. A specialist will get back to you to arrange a demo.

Chat on WhatsApp