Dograh - The open source VAPI alternative

@dzaitzow - Thank you so much for the kind words.

We strongly believe that once Dograh is into consideration of every company in the world for their voice AI use case, revenue will be an organic side effect of that. The primary focus right now is to be able to create as much value as possible for our early believers and customers to cement our place in this industry and market.

Enterprise tickets are of course something thats super welcome and helps us bring the revenue numbers up, and some of very large enterprises (Bn $$+) have told us that they are self hosting Dograh for their use case.

great question   @dzaitzow  :D
We are believers in OSS and isn't that how the dev ecosystem should always be - open and accessible :)
For monetisation - we are walking the shoes of great oss project in the past. A bunch os companies use our cloud simply because they have the optionality to switch to Open source when required

@dzaitzow We monetize through managed cloud hosting, usage-based infrastructure, and enterprise support. Self-hosting remains fully open source, while larger teams can pay for convenience, scale, and hands-on help.

@zakiah_hashim - Thank you for your message.

Two things are different - 1. Quality of the audio. Audio over browser is sampled at a higher sample rate compared to telephony - typically at 24k Hz compared to 8k Hz. 2. Signaling - Telephony has a better backbone infrastructure for faster signaling and data routing. It gets lower latency RTT compared to browser.

@zakiah_hashim thanks for asking this. You definitely get better audio quality and you can integrate on any web based system (website/app) using our add to website widget in the settings within any agent

@zakiah_hashim Thank your for support and question.

Another big practical difference is that the browser call doubles as your test mode. You can try unpublished changes to a bot straight from the dashboard without dialing in or redeploying, which makes iterating much faster.

The other change is how context reaches the agent: on a phone call it comes through the telephony layer(if inbound) or the API trigger, whereas in a web call you inject it yourself via template context variables.

We recently added the ability to simulate call direction (inbound vs outbound) there too, so you can reproduce a real scenario before going live or spending time and extra money on the telephony costs.

@zakiah_hashim Browser calls typically offer higher-quality audio, while phone calls usually have lower latency. Browser calls also support website or app integration and let you test unpublished agent changes directly from the dashboard.

@shikhil_kumar_gupta - Thank you for your comment.

Yes definitely. Dograh has excellent support for Tool Calls which enables the voice agents to be able to call APIs and interact with external systems during the course of its conversation.

@shikhil_kumar_gupta Yes, Dograh agents can call APIs using tool calls and take actions in external systems during a conversation.

@shikhil_kumar_gupta Thank you for a this question. Beyond generic tool calls, Dograh is MCP-native, so you can plug your agent into any existing MCP server and it inherits those tools without you writing custom glue for each API. And because agents are multi-step, you can trigger a specific action at the right point in the flow like look up an account during verification, book the slot after qualifying, warm-transfer to a human when needed.

Do try us and we would love to hear your feedback on this. A lot of our clients as well as us have found the MCP tool really powerful in designing an agent efficiently.

Thanks @shikhil_kumar_gupta . Dograh has inbuilt tool calling for API calls and MCP calling. you can create tools and attach them to your voice agent (with simple english instructions on when to make a particular tool call). The agnet invokes the right tool to make an MCP/API call to any external system as required.

@bobaikato - Thank you for your comment.

Inbound volume needs to scale more dynamically and is not in operator's control while outbound volume can be controlled by the operator.

Example: If there is a big event in town, a car dealership might get many more calls than they usually do on a normal days.

So, when it comes to scaling, the inbound needs to be more elastic and responsive, while the scaling requirements for outbound can be preplanned and provisioned.

Thats an excellent question @bobaikato 
Its mostly around agent building.
In general more receptive about AI agents in inbound calls( e.g. Customer support etc) rather than outbound calls (e.g. Insurance reminder etc)
In outbound we have seen that obsession around getting the first 15 seconds right works best. While in inbound scoping and being abl to handle variety of queries and handoff ecomes critical.

@bobaikato Inbound requires elastic capacity because call volume can spike unexpectedly. Outbound is easier to forecast and provision since the operator controls the call volume.

@nihalkumar_dwivedi Yes, agencies and developers can white-label Dograh, deploy it for customers, and charge under their own pricing model.

@nihalkumar_dwivedi - Thank you for your message.

Yes, @Dograh comes with a very permissive licence that allows you to self host and white-label the solution and use it for commercial purposes.

You can also use our hosted platform as a headless API provider if you have smaller volume to start with and then move on to self host on your own infrastructure as the volume grows.

@nihalkumar_dwivedi One practical thing worth adding: because it's self-hosted, you can stand up an isolated deployment per client (on-prem or in their VPC) and brand it end to end. That's a real selling point for regulated customers - you can tell them their calls, recordings and transcripts never leave their own boundary, which is often what closes the deal at your own pricing.

@yahia_bakour3 - Thank you so much for your support.

Wishing you loads of luck with @Context.dev

@yahia_bakour3 Thank you for the support!

@yahia_bakour3 Thanks for the support! Wishing Context.dev the best!

@rahul_dalmia4 - Thank you for your comment.

Not right now. But this is one of the growth engine that we have thought about in the past.

Thanks @rahul_dalmia4 . We will be adding templates in the coming weeks - as of now a template marketplace doesnt exist.
Having said that you can create any voice agent template from the agent builder itself in <60seconds. Or even better, we have amazing MCP that can build a ready to go voice agent within minutes.

@rahul_dalmia4 Not yet. We’re planning to add agent templates in the coming weeks, with a marketplace as a future possibility.

@iamyuhanliu - Thank you for you comment.

Yes, ability to self host enables you to own your stack completely.

Thanks @iamyuhanliu . we are strong believers in open source and intent to launch more powerful features in the communication stack int he coming days

@iamyuhanliu Thanks, Yuhan! Self-hosting and model choice are central to keeping the stack flexible and fully under your control.

@productrambler - Thank you for your comment.

Please reachout to us if you need any help setting up Dograh. All the best with @Mira

@productrambler Thanks for the support! Flexibility and control are exactly why we built Dograh.

Thanks @mladen_petrovic 
I hope you build something amazing - keep us posted. We are launching more stuff in the coming weeks for self hosters- including ai chat converstaions, full observability evals for voice agents and more. Do keep an eye on our upcoming launches

@mladen_petrovic Thanks! Glad Dograh’s self-hosting and local model support fit what you need.