OmniOps and HPE sign an MoU on sovereign AI in Saudi Arabia
Category: AI & Data
By Emily Carter
Published: 2026-09-04T07:30:00.000Z
The two companies signed a memorandum at LEAP to pair HPE's Saudi-made hardware with OmniOps' Bunyan inference platform in a stack that runs entirely inside Saudi jurisdiction. It is a memorandum, not a contract, and no customer, value or timeline has been published.
OmniOps and Hewlett Packard Enterprise have signed a memorandum of understanding to develop sovereign AI offerings in Saudi Arabia, announced at LEAP 2026. The arrangement pairs HPE's Saudi-made infrastructure with OmniOps' locally developed AI platforms and its in-country deployment capability, with the stated aim of giving government and enterprise buyers an AI stack that runs entirely within Saudi jurisdiction. It is worth being precise about what was signed. A memorandum of understanding sets out an intention to work together. It is not a contract, and the companies have not published a customer, a contract value, a capacity figure or a delivery timeline. What exists today is a defined technical proposition and two named parties, which is a real thing but a different thing from a deployment. The proposition itself is specific enough to assess. The joint offering is described as a full local stack, running from servers and infrastructure through to the enterprise management layers above them, aligned with HPE's Saudi Made, Developed and Deployed initiative. OmniOps' contribution is anchored on Bunyan, its AI inference platform, which the company says lets organisations deploy and manage AI workloads across cloud, on-premises and air-gapped environments according to their security, regulatory and operational requirements. The air-gapped part is the tell. Sovereignty in AI procurement is often reduced to a question of where the data centre sits, which is the easiest requirement to satisfy and the least demanding one. Buyers with genuinely restrictive obligations, in defence, security, parts of government and some regulated financial activity, need a stack that can run with no path to the public internet at all, and that constraint shapes everything above it: how models are loaded, how the platform is patched, how observability works and who holds the keys. A vendor that can run disconnected is selling to a materially different customer than one that is simply hosting in Riyadh. The commercial logic runs in both directions. HPE gets a local software layer to put on top of hardware that it is positioning as Saudi made, which is the part of the localisation argument that infrastructure vendors have historically struggled to answer. Assembling servers in the Kingdom is a supply chain achievement. Being able to say that the management and inference layers on top are also built locally, by a Saudi company, and can be operated by Saudi staff inside the country, is the harder claim and the one that carries weight in government procurement. OmniOps gets distribution and hardware certification it would take years to build alone. OmniOps was already named alongside ShaheenAI and MOZN as one of the founding software partners of HPE's Saudi initiative, which TechScoop reported at LEAP. This memorandum is a narrower bilateral agreement on the sovereign AI stack specifically, sitting inside that wider partner programme rather than replacing it. Readers should treat the two as related announcements from the same week rather than as separate commercial events. Sovereign AI was one of the most heavily used phrases at LEAP 2026, and it covers a wide range of actual arrangements. At one end sits a foreign hyperscaler operating a region inside the country under local law. At the other sits a stack where the hardware, the platform software, the models and the operations staff are all domestic. Most announcements land somewhere in between, and the distinctions are rarely made explicit in the press release. In this case the companies have been comparatively clear about the technical shape of what they intend to build, and comparatively quiet about whether anyone has agreed to buy it. That is the gap to watch. The measure of this memorandum will not be the signing but the first named deployment: a government entity or regulated enterprise running production workloads on the joint stack, with a stated environment, a stated scale and a date. Until one of those appears, this is an agreed direction between two companies with complementary gaps in their offerings.