The platform
How devices, the shared asset record, rules and open APIs fit together into one operational foundation.
Resources
Knowledge for people building connected operations.
Practical guides, a working glossary and straight answers — written by the team that ran operations before building the platform. Everything is here on the page, free to read.
- In-depth guides
- 6 practical guides
- Glossary
- 24 IoT terms explained
- Buyer questions
- 8 answered
/ Topic hubs /
Start from the question you already have.
Each hub points to the pages that answer it in depth.
Fleet and journey safety
Tracking, driver behaviour and journey controls for fleets moving people and goods across the Kingdom.
Industrial operations
Condition monitoring, maintenance and field work for plants, energy assets and public infrastructure.
Compliance and sovereignty
Data residency, deployment choices and temperature-sensitive operations where records must stand up to scrutiny.
Building on IoT Cube
See products already running on the platform, and talk to us about building your own.
/ Guides /
Practical guides, read right here.
Filter by what you are working on, then open a guide to read it in full with its checklist.
/ Glossary /
The vocabulary of connected operations, in plain language.
Protocols, networks and operating terms you will meet in any IoT project.
- CAN bus
- Controller Area Network, the internal communication network in most vehicles and much industrial machinery. Telematics devices can read CAN data for fuel use, engine hours, RPM and fault codes.
- Cold chain excursion
- Any period when a temperature-sensitive product goes outside its permitted range during storage or transport. Excursions must usually be recorded, investigated and may require stock to be quarantined.
- Condition-based maintenance
- Servicing equipment when measured condition — vibration, temperature, pressure, runtime — indicates it is needed, rather than on a fixed calendar. Aims to reduce both unexpected failures and unnecessary servicing.
- Data residency
- The requirement or practice of storing and processing data within a specific country’s borders. In Saudi Arabia, it is shaped by national regulation, sector rules and contractual obligations.
- Digital twin
- A live digital representation of a physical asset, site or process, combining its static record with current sensor data, so its state can be monitored, analysed and simulated.
- Edge computing
- Processing data close to where it is generated — on a device or local gateway — rather than in a central cloud. Reduces latency and bandwidth, and keeps sites running when connectivity drops.
- Geofence
- A virtual boundary drawn around a location, such as a depot, customer site or restricted zone. Entering, leaving or dwelling inside it can trigger rules, alerts or records.
- Journey management
- The planning, approval, monitoring and close-out of road journeys to control risk, covering route, driver fitness, rest breaks, check-ins and response when a journey goes off plan.
- LoRaWAN
- A low-power, long-range wireless protocol using unlicensed spectrum. Devices communicate with gateways that an organisation can deploy itself, making it useful for campuses, farms and sites with limited cellular coverage.
- LwM2M
- Lightweight Machine-to-Machine, an OMA SpecWorks standard for remote device management and telemetry. Commonly used with low-power devices for configuration, firmware updates and monitoring over constrained networks.
- MQTT
- A lightweight publish–subscribe messaging protocol widely used for IoT. Devices publish messages to topics on a broker, which forwards them to subscribers. Well suited to constrained devices and unreliable networks.
- MTBF
- Mean Time Between Failures: the average operating time between breakdowns of a repairable asset. Used to compare reliability and to judge whether maintenance changes are working.
- Multi-tenancy
- An architecture where one platform serves many separate customers or business units, each with isolated data, users and configuration, while sharing the underlying infrastructure.
- NB-IoT
- Narrowband IoT, a low-power cellular technology running on licensed spectrum. Designed for devices sending small amounts of data infrequently, such as meters and sensors, with good indoor penetration and long battery life.
- NFC fleet card
- A contactless card or tag used to authorise and record fleet spending, such as fuel or car care, linking each transaction to a vehicle or driver for control and reconciliation.
- OBD-II
- On-Board Diagnostics, a standard vehicle port and set of diagnostic codes, common on light vehicles. Plug-in devices use it to read speed, engine data and fault codes without complex installation.
- OPC UA
- Open Platform Communications Unified Architecture, a vendor-neutral industrial standard for secure data exchange between machines, controllers and software, common in manufacturing and process industries.
- OTA update
- Over-the-air update: delivering firmware or configuration changes to devices remotely. Good practice includes staged rollouts, verification and the ability to roll back a faulty release.
- RFID
- Radio-Frequency Identification, which uses tags read wirelessly by readers. Passive tags need no battery and suit inventory and gate checks; active tags broadcast and offer longer read ranges.
- RTLS
- Real-Time Location System, used to locate assets or people indoors or within a defined site, typically using BLE, UWB, Wi-Fi or RFID infrastructure where GPS does not work reliably.
- SCADA
- Supervisory Control and Data Acquisition, industrial systems used to monitor and control plants, pipelines and utilities. IoT platforms often integrate with SCADA rather than replacing it.
- Telematics
- The collection and transmission of data from vehicles and mobile assets, typically location, speed, engine data and driver behaviour, used to manage fleets, safety, fuel and maintenance.
- Time-series data
- Measurements recorded against timestamps, such as temperature every minute or location every few seconds. Most IoT data takes this form and needs storage optimised for high write volumes and time-based queries.
- Webhook
- An HTTP callback that sends data to another system automatically when an event occurs, such as posting an alert to a ticketing tool, without that system needing to poll for changes.
/ 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.
/ Questions /
What buyers ask us first.
Do we need to replace our existing devices?
Usually not. IoT Cube is built to connect mixed hardware and carriers, so existing trackers, sensors and meters can often be onboarded. We assess your estate during scoping and tell you plainly if a particular device is unsuitable or would be costly to integrate.
Where is our data stored?
IoT Cube is designed for data to remain in Saudi Arabia. You can deploy on sovereign cloud, private cloud, on-premises or at the edge, depending on your requirements. We document the arrangement during scoping so your security and legal teams can review it.
How long does it take to get started?
It depends on scope, hardware and integrations. A focused pilot on devices we already support moves faster than a multi-site rollout needing new integrations. We agree a realistic plan with you after scoping rather than quoting a generic timeline.
Can we integrate with our ERP, maintenance or dispatch systems?
Yes. IoT Cube provides open APIs and webhooks so data and events can flow into the systems your teams already use. Integration effort varies by system, so we review your stack early and agree what connects in each phase.
Are we tied to a particular AI provider?
No. The platform is AI-neutral, so you can use the models that suit your requirements, including ones hosted in the Kingdom or on your own infrastructure, and change them later without rebuilding your data foundation.
Should we start with a product or with the platform?
If a ready product such as tracking.me or JMS fits your need, start there — it runs on the platform, so you can extend later. If your requirements span several use cases or you are building your own product, start with the platform directly.
How is IoT Cube priced?
Pricing depends on deployment model, the number of connected assets and the products or modules you use. Our pricing page explains the structure, and we provide a specific quote once scope is clear.
Does IoT Cube meet Saudi cybersecurity requirements?
The platform is designed to align with frameworks such as the NCA Essential Cybersecurity Controls and PDPL expectations. Obligations differ by organisation and sector, so we work alongside your compliance team and recommend confirming your specific position with legal counsel.
Bring us the decision that takes too long today.
Start with the problem. IoT Cube provides the foundation underneath.