IoT Software Development Company in Riyadh, built to ship.

You cannot recall the firmware

Over-the-air update has to work before the first unit ships, including staged rollout, rollback and what happens when power is lost mid-flash. A fleet without reliable OTA is a fleet you can never fix. We track more than thirty thousand vehicles, and the update path was designed before the telemetry was.

Disconnection is the normal state, not the error state

A device in a basement, a tunnel or a dead cell is offline routinely. It buffers locally, it reconciles on reconnect, and the server distinguishes a device that is quiet from a device that is gone. Treating every gap as an alert produces alarms nobody reads.

Time-series volume breaks ordinary databases

Thousands of devices reporting every few seconds becomes billions of rows quickly. Retention, downsampling and what a query actually needs at each age of the data are design decisions taken before the first row lands, not after storage costs surprise someone.

Provisioning and identity at scale

Every device needs a credential, a rotation path, and a way to be revoked when it is stolen or decommissioned. Shared secrets across a fleet are the failure that turns one compromised unit into all of them.

Working overlap

6.5 hours a day

Two and a half hours behind Surat. A Riyadh afternoon is a Surat evening, so the second half of the day is shared and the first half is ours to build in.

The law that applies

the Saudi Personal Data Protection Law, enforced by SDAIA

The PDPL sets conditions on transferring personal data outside the Kingdom, and for several categories the practical answer is that the data stays in-Kingdom. That is a hosting decision, and it has to be made before the first migration runs, not after.

Where the data can live

Google Cloud runs a Dammam region and Oracle has Jeddah capacity, and hyperscaler investment in the Kingdom has moved quickly. Because the PDPL pushes several data categories toward staying in-Kingdom, region availability is not a performance question here, it is a legal one, and it should be settled before the schema is designed.

Sectors that dominate

Government digital transformation programmes, energy and the industries clustered around it, healthcare, and a fast-growing retail and delivery layer. A striking share of the market is driven by published national targets rather than by ordinary commercial demand.

The mistake we see most

Teams underestimate Arabic. Right-to-left is not a stylesheet flag: it changes iconography, form flow, charting, PDF generation and how numerals render inside mixed text. Building English-first and localising later is the single most expensive mistake on Saudi projects, and it is usually discovered at UAT.