dograh

dograh-hq/dograh

Open source voice AI platform. Self-hosted alternative to Vapi and Retell. On Prem, BYOK across Speech to Speech or LLM/STT/TTS, with a visual workflow builder, MCP native and telephony support.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
16 Nov 2026
4 days ago
Ship score
72/100
How it is calculated →
Stars, last 7 weeks
no history yet
No weekly sample has been taken for this repository yet.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repository facts

Stars
6.2K
Forks
1.6K
Open issues
123
Watchers
47
Primary language
Python
Created
9 Sep 2025
Owner
dograh-hq · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 141 startups in the directory ship primarily in Python.

Topics

#ai-calling#asterisk-ari#conversational-ai#inbound-calls#local-llm#no-code#on-prem-voice-agent-platform#open-source#open-source-voice-ai#outbound-calls#pipecat#python#self-hosted#speech-to-speech#speech-to-text#telephony#text-to-speech#vapi-alternative#voice-agents#voice-ai-platform

How Jev classified this project

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 19 Nov 2026 — os_startup 100%, self-hostable 94%, hosted offering 69%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 19 Nov 2026, found by the weekly discovery job at confidence 1.00. Answered by jev-1.14.0. How the classification works →

Add the status badge to your README

OSSEAN ship status: shipping — last push 16 Nov 2026This is the badge for dograh-hq/dograh, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/dograh-hq/dograh.svg)](https://ossean.com/dograh-hq/dograh)

Updates daily, from the last push GitHub saw.

The badge links to this profile, even after a GitHub rename. GitHub caches README images, so the badge can take a little longer to update there.