[verdict][prompt curatoriat][sursă: vapi.ai][traducere: la coadă]
Pot să vibecodez Vapi?
// se construiește într-un weekend, dar rămân goluri reale
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.
încredere: ridicată
ce e: API-first platform for inbound and outbound phone and web voice agents
Indice de constructibilitate · joc editorial
- Preț la consum greutate: zero
- Timp un weekend pentru un agent inbound; operare continuă în producție greutate: plus 2
- Categorie unelte pentru dezvoltatori nu cântărește
- Moat scara infrastructurii · integrări greutate: minus 3
- Încredere ridicată greutate: plus 1
- Ce pierzi 5 elemente greutate: minus 2
- Site vapi.ai (si apre in una nuova scheda) nu cântărește
Moat-ul cântărește mai mult decât prețul: refăcut, e un proiect, nu o seară.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
Ce construiești
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.
ce îți trebuie
- 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.
Promptul
Un weekend cu un agent de coding. Golurile care rămân sunt mai jos, la „ce pierzi”.
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. Prompt curatoriat: scris și revizuit manual pentru această aplicație. În engleză intenționat — e limba în care agenții de coding se descurcă cel mai bine.
Ce pierzi
- 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
De ce se plătește în continuare
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.
moat: Scara infrastructurii Integrări ce e un moat
managed realtime and telephony operations plus control plane
Alternative gratuite
N-ai chef să ți-o construiești? Astea există deja, sunt gratuite sau open source, și le-am verificat una câte una.
Respinse (1) — și de ce
- Pipecat (si apre in una nuova scheda) — A well-maintained framework for building voice agents, not an install-and-use voice-agent product.
Cine l-a construit deja
Să pornești de aici e tot vibecoding: promptul e pentru când o vrei exact în felul tău.
- LiveKit Agents + SIP (se deschide într-o filă nouă) — Apache-2.0 realtime agent framework. Pair it with the separately deployed LiveKit Server and SIP service for a self-hosted phone stack. (alive)
- Pipecat (se deschide într-o filă nouă) — BSD-2-Clause Python framework with composable voice pipelines and broad model, transport, and telephony integrations. You still own deployment and carrier operations. (alive)
- Voice OSS cost planner (se deschide într-o filă nouă) — Source-linked calculator and deployment reference for platform, model, SIP, number, infrastructure, and operational costs. It is a planning companion, not an agent runtime. (alive)
Ești de acord?
Balanța voturilor
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.