Dograh

Dograh

Open-source, self-hostable voice AI platform for building speech-to-speech agents with your own model keys.

63/100MonitorCustom pricingContact Sales

Dograh makes sense for exactly one kind of buyer: a team with engineering capacity that cannot put call audio and transcripts in a third-party cloud. Self-hosting plus BYOK for STT, TTS, and LLM, MCP-native context, and Twilio telephony is a coherent stack for that constraint, and the enterprise offer to deploy inside your environment is a direct answer to data-residency reviews. If you don't have the bench to own latency and uptime for live calls, a hosted voice-agent vendor will get you to production faster.

Verified 4d ago · liveness 63/100 · cite: rightaichoice.com/tools/dograh

Best for
  • Developers building custom voice agents with full data control
  • Enterprises needing on-prem or in-environment deployment for compliance
  • Teams using BYOK to keep model choice and avoid per-call billing
  • Platform teams that already run their own infrastructure and want a visual flow builder
Not ideal for
  • Non-technical users who want a fully managed SaaS voice product
  • Teams with no infrastructure or DevOps capacity to self-host
  • Buyers who need pre-built, no-code voice agents out of the box
Visit Website

AdvancedDevelopers already running infrastructure should budget a day or more for a first working agent: deploy the open-source stack, connect STT, TTS, and LLM keys, attach a Twilio number, and build one flow in the visual builder. Regulated enterprises doing an in-environment deployment have a longer path that includes security review and data-perimeter sign-off. Non-technical teams will find theWeb · APIAPI availableVerified 4d ago
Pricing
Custom pricing
Contact Sales4 hidden costs
Learning curve
Advanced
Developers already running infrastructure should budget a day or more for a first working agent: deploy the open-source stack, connect STT, TTS, and LLM keys, attach a Twilio number, and build one flow in the visual builder. Regulated enterprises doing an in-environment deployment have a longer path that includes security review and data-perimeter sign-off. Non-technical teams will find the
Runs on
WebAPI
API available · 1 integrations
Who it's for
Platform engineer at a regulated companyDeveloper prototyping a voice agentIT team running an internal helpdesk
Live sentiment
Is Dograh actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip Dograh if you want a hosted voice-agent vendor to own uptime and latency, or if your team has no capacity to run STT, TTS, and LLM endpoints yourself.

The 30-second take
Biggest gripe

Self-hosting shifts the per-call meter to your own infrastructure bill — compute, bandwidth, and storage for call recordings and transcripts land on your cloud account.

Price reality

Dograh is priced as a self-hosted, open-source stack rather than a per-minute hosted agent, so cost scales with your own infrastructure and BYOK provider usage instead of a seat or minute meter. That fits engineering-led teams and regulated enterprises comparing against hosted voice-agent vendors that charge per call minute. Teams without the infra capacity to absorb that should compare against fully managed voice platforms before committing.

In short

Dograh — Open-source, self-hostable voice AI platform for building speech-to-speech agents with your own model keys. Best for Developers building custom voice agents with full data control, Enterprises needing on-prem or in-environment deployment for compliance, Teams using BYOK to keep model choice and avoid per-call billing. Contact Sales pricing.

What people actually say about Dograh — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

56 mentions across 5 sources (Hacker News, YouTube, Bluesky, GitHub, Lemmy) · researched Jul 27, 2026.

75% positive25% critical

Average across the 5 sources that answered — each source counts once, not each post.

Recurring strengths
  • +Eliminates costly per-minute platform fees from Vapi/Retell.
  • +Visual workflow builder similar to n8n for voice AI.
  • +Fully self-hosted with bring-your-own-keys for all models.
  • +Supports both speech-to-speech and LLM/STT/TTS pipelines.
  • +Active development with frequent feature releases and bug fixes.
Recurring frustrations
  • −Steep learning curve for users without self-hosting experience.
  • −Documentation is sparse and community-driven, not comprehensive.
  • −Latency depends heavily on user infrastructure and LLM providers.
  • −No managed cloud option; everything must be self-hosted.
  • −Limited integrations beyond Twilio and model APIs.
Patterns worth knowing
Cost savings vs. Vapi/Retell is the main driver
Seen on Hacker News, Bluesky, Lemmy
Self-hosting complexity is a barrier
Seen on Hacker News, YouTube, Lemmy
Visual workflow builder compared to n8n is well-received
Seen on Hacker News, Lemmy, GitHub
Learning curve
advancedProductive in ~Days of setup
Hidden costs people mention
  • • You pay for your own cloud servers or on-prem hardware.
  • • API costs for STT, TTS, and LLM models are separate.
  • • Twilio fees for telephony integration.

Viability Score

63/100
Monitor

How well maintained and how widely used is Dograh? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
not measured
Traction
100
Site health
95
User sentiment
75
What the vendor publishes
0

Last calculated: October 2026

How we score →

Key Features

  • Self-hosted deployment on your own infrastructure
  • On-premises and in-environment deployment for regulated teams
  • BYOK - bring your own keys for STT, TTS, and LLM providers
  • Speech-to-speech voice agent pipelines
  • Composed LLM + STT + TTS pipeline building
  • MCP-native agent context via Model Context Protocol
  • Visual drag-and-drop workflow builder for conversation flows
  • Twilio telephony for live voice calls
  • Multi-tenant agent management from a single instance
  • Web dashboard for configuration and monitoring
  • REST API for wiring agents into external systems
  • Real-time conversational voice agents
  • Open-source codebase
  • Custom model support through BYOK
  • Google sign-in for platform access

About Dograh

Contact SalesAdvancedAPI availableWeb · API

Dograh is an open-source voice AI platform you run inside your own infrastructure instead of renting per-minute agents from a hosted vendor. Its own shorthand for the stack is "speech-to-speech, MCP-native, BYOK - any model" — you bring your own speech-to-text, text-to-speech, and LLM keys rather than being locked to one provider. Conversational flows are assembled in a visual drag-and-drop workflow builder, so branching logic doesn't require code for every turn, and you can run either a direct speech-to-speech pipeline or a composed LLM + STT + TTS chain depending on which models you want in the loop. Twilio handles telephony so agents can take live calls, a web dashboard covers configuration and monitoring, and multi-tenant management lets one instance serve several teams or use cases. MCP-native support means agents pull external context through the Model Context Protocol. The audience is technical: developers and platform teams building custom voice agents, plus enterprises in regulated industries that need on-prem deployment, data residency, and a defined data perimeter — Dograh explicitly offers to deploy inside your environment for regulated and high-scale teams. The trade is straightforward: self-hosting with BYOK removes the per-call meter hosted voice-agent vendors charge, but you inherit model selection, latency tuning, uptime, and the DevOps work behind all three.

Behind the Verdict

Dograh's pitch is narrow and internally consistent: the open-source voice AI platform where you self-host and bring your own model keys. Read that literally and everything else follows. Strengths are concentrated in control. The stack is speech-to-speech or a composed LLM + STT + TTS chain of your choosing, which means model quality is your selection to make rather than a vendor's bundled default. The visual drag-and-drop workflow builder handles branching conversation logic without code for every turn, which matters a lot when call flows get long — hand-writing state machines for IVR trees gets old fast. Twilio covers telephony, so agents can take live calls without you standing up SIP infrastructure first. MCP-native context lets agents reach external systems through the Model Context Protocol rather than a bespoke tool-calling layer. Multi-tenant management from a single instance means one deployment can serve several teams or use cases, and the web dashboard covers configuration and monitoring without you building an ops console. The REST API is how agents reach systems you already run — CRM lookups, ticket creation, whatever the call needs. And the enterprise offer to deploy inside your environment is the piece regulated buyers actually evaluate on: data residency and a defined perimeter, with call audio and transcripts never leaving your infrastructure. The honest weaknesses are the mirror image. Self-hosting is not a checkbox; you own uptime, latency, scaling, and model quality, and there is no managed fallback when your infrastructure misbehaves. Because you supply STT, TTS, and LLM keys under BYOK, output quality tracks your own provider choices — a weak TTS model sounds weak, and no amount of workflow polish hides it. Twilio is the telephony path surfaced in the vendor content, so plan around it rather than assuming a broad telephony marketplace. Dograh is an early-stage open-source project, so expect to contribute some of your own documentation and operational know-how rather than inheriting a mature playbook. Where it fits: engineering-led teams with a compliance constraint, platform teams already running their own infrastructure who want a visual flow builder on top, and anyone whose per-call bill from a hosted voice-agent vendor has become the problem. Where it doesn't: non-technical buyers who want a no-code voice agent out of the box, and teams without DevOps capacity to run live call infrastructure — for them a managed platform is the correct answer even at a per-minute premium.

Researching Dograh? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Real-world workflow fit

Concrete scenarios for the personas Dograh actually fits — and what changes day-one when you adopt it.

Platform engineer at a regulated company

You stand up Dograh inside your own VPC, plug in your LLM, STT, and TTS keys, connect a Twilio number, and build a support call flow in the drag-and-drop builder with an MCP connector to your internal knowledge base.

Outcome: Live support calls are answered by an agent whose audio and transcripts never leave your perimeter, satisfying the data-residency review.

Developer prototyping a voice agent

You prototype a speech-to-speech lead qualification flow in the visual builder, then wire the collected answers into your CRM through the REST API.

Outcome: A working qualification agent that writes structured lead data into systems you already run, without paying a per-call vendor meter.

IT team running an internal helpdesk

You deploy one multi-tenant Dograh instance and give HR and IT separate tenants, each with its own voice workflow over internal-only data.

Outcome: Two teams share one self-hosted deployment and one ops surface instead of separate vendors.

Use Cases

  • Build a self-hosted customer support voice bot using your own LLM and TTS keys
  • Deploy a lead qualification voice agent that reaches your CRM through the REST API
  • Run an internal HR or IT helpdesk voice assistant over on-premises data
  • Prototype speech-to-speech conversation flows with custom intents
  • Combine MCP-driven context with Twilio telephony for interactive voice response
  • Stand up multi-tenant voice agents for several teams from one self-hosted instance

Limitations

  • Self-hosting is the central trade-off: you own uptime, latency, scaling, and model quality, and there is no managed fallback if your infrastructure misbehaves.
  • Because you supply STT, TTS, and LLM keys under BYOK, output quality tracks your own provider choices.
  • Twilio is the telephony path surfaced in the vendor content — plan around it rather than assuming a broad telephony marketplace.
  • Dograh is an early-stage open-source project, so expect to contribute some of your own documentation and operational know-how rather than inheriting a mature playbook.
  • Running live voice calls in-house also means latency tuning sits with you: speech-to-speech pipelines have to be dialed in for your own network and model endpoints.

as of 2026-10-14

Verification history

We have re-verified Dograh 10 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
  2. — re-checked, vendor evidence unchanged
  3. — re-checked, vendor evidence unchanged
  4. — re-checked, vendor evidence unchanged
  5. — re-checked, vendor evidence unchanged
  6. — re-checked, vendor evidence unchanged

Showing the 6 most recent of 10 verification passes.

Free to cite with attribution — this page re-verifies continuously.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • Self-hosting shifts the per-call meter to your own infrastructure bill — compute, bandwidth, and storage for call recordings and transcripts land on your cloud account.
  • Because you supply STT, TTS, and LLM keys under BYOK, your provider's usage charges sit on top of everything else, and they scale directly with call volume.
  • Twilio telephony is billed separately by Twilio for phone numbers and call minutes, so the telephony layer carries its own meter outside Dograh.
  • Running live voice calls in-house means engineering time for latency tuning, model swaps, and on-call coverage when calls fail — a headcount cost, not a line item.

Where the pricing makes sense

The company stage and team size where Dograh's pricing actually pencils out — and where peers do it cheaper.

Dograh is priced as a self-hosted, open-source stack rather than a per-minute hosted agent, so cost scales with your own infrastructure and BYOK provider usage instead of a seat or minute meter. That fits engineering-led teams and regulated enterprises comparing against hosted voice-agent vendors that charge per call minute. Teams without the infra capacity to absorb that should compare against fully managed voice platforms before committing.

Setup time & first value

How long it actually takes to get something useful out of Dograh — broken out by persona, not the marketing-page minute.

Developers already running infrastructure should budget a day or more for a first working agent: deploy the open-source stack, connect STT, TTS, and LLM keys, attach a Twilio number, and build one flow in the visual builder. Regulated enterprises doing an in-environment deployment have a longer path that includes security review and data-perimeter sign-off. Non-technical teams will find the

Switching to or from Dograh

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From a hosted voice-agent vendor: rebuild your call flows in Dograh's drag-and-drop builder and repoint Twilio numbers at your own deployment.
  • →From a hand-rolled speech pipeline: keep your existing LLM, STT, and TTS keys, then move branching call logic into the visual workflow builder.
  • →From an in-house IVR: replace the scripted tree with MCP-driven context and a speech-to-speech or composed pipeline you host yourself.
Migrating out
  • ↗To a managed voice-agent platform: hand your call flows and transcripts to a hosted vendor and give up self-hosting and BYOK in exchange for managed uptime.
  • ↗To a hand-rolled speech pipeline: export your conversation logic and run it against your own orchestration if the visual builder becomes a constraint.

Integrations

Twilio

Resources & Guides

Tutorials & Learning

YouTube returned 6 videos for “Dograh”, and we withheld 6: 6 could not be judged, because “Dograh” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Dograh.

Official links

Tools that pair well with Dograh

Common stack mates teams adopt alongside Dograh, with the specific reason each pairing earns its keep.

Featured Head-to-Head Comparisons

Alternatives to Dograh

View all
Inworld

Inworld

Inworld delivers realtime text-to-speech, speech-to-text, and open-model inference on one API for consumer voice apps.

FreemiumTry
PolyAI

PolyAI

PolyAI builds enterprise voice AI agents that resolve complex customer calls end to end in 40+ languages.

Contact SalesTry
Synthflow AI

Synthflow AI

Synthflow AI runs enterprise voice AI agents on its own telephony network for automated phone calls at scale.

PaidTry

Frequently Asked Questions

Used Dograh? Help shape our editorial sentiment research.