Vapi vapi.ai

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.

Verdict: Half-bot · AI gets you partway; the hard part stays hardBuild time: weekend for one inbound agent; ongoing production operations
Half-bot

01What it costs

Price variesBuild, usage based per call minute

Checked Aug 14, 2026 · source: vapi.ai.

PlanMonthlyBilled yearlyWhat you get
BuildFree—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

Dograhopen-source

A Vapi-shaped workflow builder you can Docker-compose; phone and model meters remain.

dograh.com →

05The build prompt

Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.

prompt.txt
Build me a focused, self-hosted alternative to Vapi for one inbound support number.
Requirements:

- Use Python 3.12 and livekit-agents~=1.5 with one named AgentServer worker.
  Use direct provider plugins, not LiveKit Inference or another managed agent host.
- Run LiveKit Server, Redis, and LiveKit SIP with Docker Compose on one Ubuntu VM.
  Put Caddy in front of HTTPS/WSS; expose only the documented SIP and UDP media ports.
- Provision one Telnyx DID and credential-authenticated SIP trunk. Include checked-in
  LiveKit inbound-trunk and dispatch-rule JSON that sends calls to support-agent.
- Build an AgentSession with Silero VAD, Deepgram Nova-3 STT, gpt-5-mini through
  the OpenAI plugin, and Cartesia Sonic-3 TTS. Load every secret from .env.
- Give the agent one narrow support prompt, interruption handling, and two tools:
  look up an order in SQLite and save a callback request after caller confirmation.
- Persist call id, timestamps, transcript, tool results, and outcome to SQLite.
  Add structured JSON logs and /healthz; recording is off by default.
- Include unit tests for both tools and scripted agent tests for lookup, refusal to
  invent an order, callback confirmation, and a caller interruption.
- Provide make setup, make dev, make smoke, and docker compose up -d commands.
  The smoke test must work in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, dispatch, provider-key, and test-call
  steps, plus common one-way-audio and SIP authentication checks.
- The cost section must say the Vapi fee is removed, while the DID, SIP minutes,
  model usage, VM, failed calls, monitoring, and operator time remain. Link the
  source-backed calculator at https://voice.oss.codes for changing rates.
- Out of scope: outbound campaigns, a multi-tenant dashboard, squads, billing,
  automatic provider failover, call recording, compliance claims, and high availability.

06Open-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.
Sponsor slot · openFeatured alternative to Vapi. A labeled card for one relevant tool.
Book this spot →

App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.