Voho runs entirely inside infrastructure you control. Call audio, transcripts, the agent’s reasoning and every record it produces stay inside your network boundary, on hardware you own or lease, in the country you choose. This is the configuration for organisations that cannot send customer conversations to a third party: regulated sectors, government, and anyone whose own contracts commit them to keeping processing in-country.
On-premise is delivered as an engagement, not a self-service download. Your environment is sized against your real call volume before anything is installed. See Getting started for what that path looks like.

​
What “on-premise” can mean

Four shapes, in decreasing order of how much you operate yourself. All four keep processing under your control; they differ in who owns the metal and whether anything reaches the internet.

Your data centre

Voho runs on your own servers, in your own building, on your own GPUs. You own the hardware and the operational responsibility.

Disconnected

Models, call handling and records all sit inside your network, and licensing is checked against a local signed file, so nothing needs to be reachable for the line to keep answering. See Licensing and egress.

Your private cloud

Your own cloud tenancy or VPC, under your accounts and your network policy, rather than shared infrastructure.

In-country hosted

A dedicated deployment in a Saudi data centre, operated for you, when in-country residency is the requirement but running it yourself is not.

​
It fits the platform you already run

A deployment starts at one GPU server and grows by adding nodes. It ships in three forms so it lands on the infrastructure you have: The hardware floor is a single modern GPU with 16–24 GB of VRAM, 8 cores and 32 GB of RAM. See Requirements.

​
What runs locally

In a self-hosted deployment, the full conversational loop runs inside your boundary:

​
What changes for your team

On-premise moves real operational work to you. That trade is worth making when an obligation requires it, and rarely worth making when it does not.

​
Choosing between on-premise and managed

Take on-premise when a specific obligation requires processing to stay inside your environment: a residency rule, a sector regulation, or a term in your own customer contracts. If the driver is a general preference for control rather than a named obligation, the managed service with the right contractual terms is usually the better trade. See Deployment options for the comparison.

​
Next

Architecture

What runs where, and what crosses the boundary.

Requirements

What your environment needs to provide.

Getting started

From scoping call to live traffic.

Data residency

Where data sits, and the evidence your auditors will ask for.