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 arrive, data gains meaning, rules become action, and whatever you build next has somewhere to stand.

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
Eleven products today

/ Architecture /

Five things a platform has to do. Most vendors do one.

Connectivity without context is a data feed. Context without automation is a report. The value is in all five working as one layer.

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 treated as a lifecycle, not a list.

03

Understand

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 eleventh use case costs a fraction of the first.

/ Modules /

Explore the platform, layer by layer.

Select a module to see what it does and how it works.

01 / Connect

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.

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

Networks

  • 4G / 5G on any Saudi carrier
  • NB-IoT & LTE-M
  • LoRaWAN
  • Wi-Fi & Ethernet
  • Satellite backhaul
  • BLE via gateway

Integration

  • REST APIs
  • Webhooks
  • Streaming export
  • ERP, WMS, CMMS & TMS connectors
  • SFTP & scheduled exports
  • Single sign-on

Data

  • Time-series telemetry
  • Events & alarms
  • Geospatial
  • Configurable retention
  • Full export — your data stays yours

Security

  • Encryption in transit and at rest
  • Tenant isolation
  • Role-based access control
  • Full audit trail
  • Device identity & credential rotation

Experience

  • Arabic & English
  • Right-to-left interfaces
  • Web & mobile
  • White-label branding

/ 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 2

Private cloud

Deployed into your organisation’s own cloud tenancy.

  • Your cloud account
  • Your security policies
  • Same product, same APIs

Option 3

On-premises

Installed in your own data centre where policy requires it.

  • Full physical control
  • Integrates with internal networks
  • Suited to regulated estates

Option 4

Edge

Processing at site for remote or disconnected operations.

  • Works through network loss
  • Local rules and alarms
  • Syncs when connectivity returns

/ Intelligence /

Bring your own model.

The platform is AI-neutral. What matters is not which model — it is that the output lands in an alert, a work order or a route change, instead of a report somebody reads on Thursday.

  • 01Anomaly detection

    Spot the reading, route or behaviour that does not fit — on live operational data.

  • 02Failure prediction

    Condition-based maintenance driven by vibration, temperature, current and usage.

  • 03Optimisation

    Consumption, demand and route optimisation that feeds straight into workflows.

  • 04Ask in Arabic or English

    Natural-language questions over your own operations, answered from your own record.

/ 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
  • Streaming export to your data platform
  • White-label portals and apps
  • Sandbox tenants for partners
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 /

Sovereign is a place, not a promise.

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 →

/ Questions /

Frequently asked.

Do we have to replace our devices?

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.

Where is our data stored?

Inside Saudi Arabia by default. Where policy requires it, the platform deploys into your own cloud tenancy or data centre without becoming a different product.

Can we use our own AI model?

Yes. The platform is AI-neutral. Run the model your organisation has approved, or ours — the output lands in an alert, a work order or a system update either way.

How do our systems integrate?

Through REST APIs, webhooks, streaming export and connectors for common ERP, maintenance, warehouse and transport systems. Your data can always be exported in full.

Can partners build products on it?

That is what it was built for. Eleven products already run on the foundation, and the same APIs, multi-tenancy and white-label options are available to partners.

Does it support Arabic?

Arabic and English, including right-to-left interfaces, from the first release.

Bring us the decision that takes too long today.

Start with the problem. IoT Cube provides the foundation underneath.

Request a Demo

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