Can AI replace Vapi?
A focused inbound agent is a credible weekend build with LiveKit Agents or Pipecat. Replacing Vapi as a product is much larger: it combines realtime orchestration, provider abstraction, phone-number and SIP workflows, outbound campaigns, tool calls, testing, observability, scaling, support, and compliance options. Self-hosting can remove Vapi's $0.05 per-minute platform fee, but model, carrier, number, infrastructure, failed-call, monitoring, and engineering costs remain.
Replacing a paid app means you set it up and keep it running: hosting, updates and backups can be on you. What you give up.
01What it costs
Checked Aug 14, 2026 · source: vapi.ai.
| Plan | Monthly | Billed yearly | What you get |
|---|---|---|---|
| Build | Free | — | At least 60 promotional call minutes at signup and 10 concurrent calls; ongoing calls are fully usage based. |
| Scale | — | — | Custom annual usage commitment, concurrency, support and volume terms. |
Hidden costs: Voice calls add a $0.05/minute Vapi platform fee plus separate speech-to-text, model, text-to-speech and telephony charges; SMS/chat is $0.005/message; extra concurrency is $10/line/month; HIPAA is $2,000/month and zero-data-retention is $1,000/month.
02Could AI build it for you?
The core job: Route a SIP trunk into a realtime agent, stream speech through STT, LLM, and TTS with interruption handling, run a server-side tool, and save the call outcome.
What a working version needs:
- public Linux VM, domain, TLS, and correctly restricted SIP, WebRTC, and RTP ports
- SIP trunk and phone number from a carrier such as Telnyx
- STT, LLM, and TTS provider API keys
- country-specific consent, recording, caller-ID, and outbound-calling review before real traffic
The orchestration fee is replaceable; dependable managed telephony operations are the harder product.
03What you'd give up
- managed realtime infrastructure, scaling, provider failover, and support
- assistant, squad, workflow, phone-number, and provider configuration APIs
- outbound campaigns, carrier integrations, spam mitigation, and production telephony debugging
- hosted simulations, evaluations, call logs, recordings, analytics, and retention controls
- enterprise SLAs, compliance add-ons, role controls, and data-residency options
They pay to move from a working voice demo to dependable production calling without operating SIP, RTP, WebRTC, agent workers, provider fallbacks, observability, and capacity themselves.
04Free and cheaper alternatives
A Vapi-shaped workflow builder you can Docker-compose; phone and model meters remain.
dograh.com →05The build prompt
The complete build prompt, plus 11 step-by-step prompts from research to launch, a design system file, a page-by-page spec, the data model and a launch checklist.
Get the Build Kit · $9 →One-time payment. Delivered on screen and by email.
06Free open-source starting points
- LiveKit Agents + SIP: Apache-2.0 realtime agent framework. Pair it with the separately deployed LiveKit Server and SIP service for a self-hosted phone stack.
- Pipecat: BSD-2-Clause Python framework with composable voice pipelines and broad model, transport, and telephony integrations. You still own deployment and carrier operations.
- Voice OSS cost planner: Source-linked calculator and deployment reference for platform, model, SIP, number, infrastructure, and operational costs. It is a planning companion, not an agent runtime.
Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.