Voho wins a landmark enterprise contract

About Voho

Enterprise AI that speaks Saudi Arabic and stays in the Kingdom.

We build the AI that Saudi organisations can actually put into production: agents that speak the dialect their customers speak, read the paperwork their operations run on, and act inside the systems they already have — on infrastructure they own.

How we think about it

Three things we will not compromise on.

The dialect is not a detail

Most Arabic AI is Modern Standard with the edges filed off — correct, and nothing like how anyone in Riyadh actually speaks. Our voices are built around Najdi, and code-switching between Arabic and English mid-sentence is treated as normal, because in the Gulf it is.

It has to run where you say

The first question in this market is where the data lives, and the honest answer cannot be "our cloud, trust us". Everything we build can run in a private deployment, in a Saudi data centre, or on servers inside your own building with no connection to the outside world.

Doing the work, not describing it

An assistant that answers questions is a demo. One that raises the request in Archibus, updates the record in SAP and reads back the reference number is a colleague. Where your rules say a person must approve something, it stops and asks.

Where we work

Built for the Kingdom, not localised for it.

Saudi Arabia's National Strategy for Data & AI sets out a path from national enabler to industry leader by 2030, with education, government, healthcare, energy and mobility as its priority sectors. Those are the sectors that run on Arabic, on paperwork, and on systems that cannot be moved to someone else's cloud.

That is the gap we build for. Not an English product with an Arabic setting, and not a cloud service with a residency checkbox — Arabic-first systems that deploy where the rules say they must, whether that is a Saudi data centre or a rack in your own building.

Everything we claim on this site can be checked before you speak to anyone: play the demos, read the code, read the documentation.

Rather than take our word for it

Three ways to check before a sales call.

Play it yourself

Every demo runs in your browser with no sign-up and no sales call — a Saudi Arabic service call, a stamped invoice being read, thirty years of engineering files being searched.

Open the demos

Read the code

Public example repositories, one per sector, showing the whole thing working — phone agents, document extraction, booking, ordering, dispatch. MIT licensed and free to run on your own infrastructure.

Browse the examples

Check the documentation

Both ways in: complete voice agents — instructions, actions, handoff, transcripts — and the Speech API on its own for teams that only need the voice. Written to be read before you buy anything.

Read the docs

Start with one workflow, on your own systems.

We build the first one with you rather than handing over a platform and a login. It is usually live within a month.