Managed cloud
The default. Voho operates the infrastructure, you connect a phone number and configure your agents. There is nothing to install and nothing to maintain, and new capabilities reach you without a deployment on your side. This suits most teams, including regulated ones — the questions worth asking are about data handling and retention rather than about who owns the hardware.If your organisation has specific requirements on processing location or data retention, raise them during scoping. The answers depend on your contract and are worth settling before you build on the platform.
On-premise
On-premise deployment runs Voho inside infrastructure you control, so call audio and transcripts are processed in your environment rather than ours. Organisations choose it for data-residency obligations, security policies that prohibit external processing of customer conversations, or contractual terms with their own clients. On-premise is scoped per engagement rather than self-served. What gets deployed depends on which capabilities you need, your expected call volume, and the hardware you have available.What a scoping conversation covers
- Capabilities — which parts of the platform run locally, and whether anything remains connected.
- Capacity — expected concurrent calls, which determines hardware.
- Environment — what you have available, and what needs provisioning.
- Operations — who runs it, how it is monitored, and how updates are applied.
- Data handling — what is retained, where, and for how long.
Choosing between them
Take on-premise when an obligation genuinely requires processing to stay inside your environment. It moves real operational responsibility to your team — capacity planning, monitoring, and updates all become yours. If the driver is general security preference rather than a specific obligation, the managed service with the right contractual terms is usually the better trade.Talk to us about on-premise
Scoping starts with your capacity and compliance requirements.