Should you build your own Thrumble?
Voice AI platform for inbound and outbound business phone calls
A single inbound receptionist agent is a credible weekend build with LiveKit Agents or Pipecat plus a SIP trunk. Thrumble as a product is larger: agent config UI, knowledge bases, tools, call transfer, outbound campaigns, phone numbers, transcripts, and production telephony. You can DIY the core conversation loop; you still own carriers, media ports, failed calls, and ops.
ENOriginal research content in English. Original prompt preserved in English.
Build me a focused self-hosted alternative to Thrumble for one inbound business number.
Requirements:
- Python 3.12 + livekit-agents with one AgentServer worker.
Direct provider plugins only · no managed agent host.
- Docker Compose: LiveKit Server, Redis, LiveKit SIP, Caddy for HTTPS/WSS.
Expose only documented SIP and UDP media ports.
- One Telnyx DID + credential SIP trunk. Checked-in inbound-trunk and
dispatch-rule JSON that routes calls to receptionist-agent.
- AgentSession: Silero VAD, Deepgram STT, gpt-4.1-mini (OpenAI plugin),
Cartesia TTS. Secrets only from .env.
- Narrow receptionist prompt: answer FAQs from a local knowledge.md,
book a callback into SQLite after confirmation, transfer is out of scope.
- Persist call id, timestamps, transcript, and outcome to SQLite.
JSON logs + /healthz. Recording off by default.
- Unit tests for FAQ lookup and callback confirmation; scripted agent tests
for interruption and refusal to invent facts.
- make setup / make dev / make smoke + docker compose up -d.
Smoke test must pass in the LiveKit agent console before a real PSTN call.
- README: DNS, TLS, firewall, Telnyx, trunk, keys, test-call steps,
and common one-way-audio / SIP auth failures.
- Out of scope: outbound campaigns, multi-tenant dashboard, knowledge-base
crawler, tool marketplace, call transfer, billing, HA, compliance claims.The prompt opens pre-filled in your agent. Review it before running.
What would building your own look like?
Answer one inbound number with a realtime STT → LLM → TTS agent, look something up, and log the call outcome.
What you will need
- public VM with TLS and correctly opened SIP / WebRTC / RTP ports
- SIP trunk and phone number (e.g. Telnyx)
- STT, LLM, and TTS API keys
- consent and recording rules for your country before real traffic
They pay to go from a demo voice loop to dependable inbound and outbound calling without running SIP, media, agent workers, numbers, campaigns, and monitoring themselves.
xhosted agent builder, knowledge bases, tools, and transfer destinations
xoutbound campaign dialer and contact workflows
xmanaged phone numbers, concurrency, and telephony debugging
xcall logs, recordings, post-call extraction, and analytics
xuptime, support, and multi-tenant workspace polish
How much does Thrumble cost?
- Monthly billing
- $99/mo$99/mo
- Per year
- $1,188/yr$1,188/yr
- On a Brazilian card, with 3.5% IOF
- R$517/moR$6,208/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Thrumble’s site. Vibe Radar does not handle payments.
Is it cheaper to build or buy Thrumble?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Building pays for itself in 24 months.
Starting hours estimated from the analysis (weekend for one inbound agent; ongoing for campaigns and production ops). Does not price what you give up (support, integrations, security).
Can I rebuild Thrumble?
Kinda. The core of Thrumble is buildable in a weekend with the prompt on this page, but there are real gaps: hosted agent builder, knowledge bases, tools, and transfer destinations, outbound campaign dialer and contact workflows. Read the honest list above before committing.
How much does Thrumble cost?
Thrumble costs about $99/mo (Starter, checked 10/20/2026), which is $1,188 per year.
What do I lose by replacing Thrumble?
Honestly: hosted agent builder, knowledge bases, tools, and transfer destinations; outbound campaign dialer and contact workflows; managed phone numbers, concurrency, and telephony debugging; call logs, recordings, post-call extraction, and analytics; uptime, support, and multi-tenant workspace polish. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Thrumble?
Yes: LiveKit Agents + SIP (Realtime agent framework; pair with LiveKit Server + SIP for a self-hosted phone stack.), Pipecat (Composable voice pipelines with telephony integrations; you still own deploy and carriers.). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.