Choose Xebit VoiceCloud or Xebit VoiceKit

Compare the managed cloud and the self hosted kit, and pick the one that fits your data, volume and team.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

Choose Xebit VoiceCloud if you want to be live quickly without running infrastructure. Choose Xebit VoiceKit if audio and transcripts must stay inside your network, if you expect more than roughly 10,000 connected minutes a month, or if you want to control the stack yourself. Both run the same platform, so moving from one to the other later is a deployment change rather than a rebuild.

At a glance

Xebit VoiceCloudXebit VoiceKit
Who runs itXebitYour team, on Docker or Kubernetes
Where it runsXebit's infrastructureYour cloud account, your data centre, or fully air gapped
Where you sign inThe dashboard at voice.xebit.aiThe admin console on your own host
API base URLhttps://api.voice.xebit.ai/v1https://<your-xebit-voicekit-host>/v1
AI modelsIncludedYour own licences, or local models on your GPUs when air gapped
TelephonyYour carrier and SIP trunksYour carrier and SIP trunks
PricingAbout $0.052 per connected minute, 5,000 minute monthly minimum (about $258), three month minimum termAnnual licence from about $4,330 plus setup from $2,062. Call volume does not change it
Concurrency and quotasSet by your Xebit VoiceCloud accountSet by your own deployment and licence band
UpdatesApplied by XebitIncluded in the licence; your team applies them

Full pricing is on the pricing page.

You currently have Xebit VoiceCloud selected in the docs switch. Pages throughout the guide show Xebit VoiceCloud steps.

You currently have Xebit VoiceKit selected in the docs switch. Pages throughout the guide show Xebit VoiceKit steps.

Where your data goes

  • Xebit VoiceCloud: audio reaches Xebit's infrastructure and the model provider. Recordings, transcripts and outcomes are stored in Xebit's infrastructure.
  • Xebit VoiceKit on prem: the platform runs inside your network. Only inference traffic leaves it, to the model provider you hold the licence with.
  • Xebit VoiceKit air gapped: models run locally on GPUs you provide and nothing leaves the network.

In every case telephony stays with your carrier. See Security for the current compliance status.

When Xebit VoiceCloud is the better fit

  • You want to build an agent and run a pilot list this week.
  • Your volume is below roughly 10,000 connected minutes a month.
  • You do not have an engineer who can own the infrastructure.
  • Your data can be processed outside your own network.

When Xebit VoiceKit is the better fit

  • Audio, transcripts and logs must stay inside your network, or nothing may leave it at all.
  • You run above roughly 10,000 connected minutes a month, where owning the licence costs less than renting the minutes.
  • You want to control deployment, scaling, monitoring and fallback yourself.
  • You have an engineer who will own it. Xebit does the first install with you, but this is infrastructure and it needs a person.

What is the same in both

The agent builder, campaigns and scheduling, the audio bridge, conversational intelligence, Observability and the SRE agent, and workflows and integrations all ship in both. The REST API and webhooks are the same apart from the base URL.

Next steps