| name | dograh |
| description | Self-hosted voice AI platform — Vapi/Retell alternative with MCP and visual workflow builder |
| tags | ["voice-ai","telephony","selfhosted","mcp","stt","tts"] |
| related_skills | ["hermes-agent"] |
Dograh — Self-Hosted Voice AI Platform
Build, deploy, and manage voice AI applications on your own infrastructure. MCP native.
Prerequisites
- Python 3.10+
- API keys for STT/TTS providers (Deepgram, ElevenLabs, OpenAI, etc.)
- Telephony provider (Twilio, Vonage) for inbound/outbound calls
Installation
git clone https://github.com/dograh-hq/dograh.git
cd dograh
pip install -e .
Configuration
export OPENAI_API_KEY=*** DEEPGRAM_API_KEY=*** ELEVENLABS_API_KEY=***
cp .env.example .env
Usage
Start the server
dograh serve --port 8080
Create a voice workflow
curl -X POST http://localhost:8080/api/workflows \
-H "Content-Type: application/json" \
-d '{
"name": "appointment-scheduler",
"voice": "alloy",
"llm": "gpt-4",
"prompt": "You are a friendly appointment scheduler. Help callers book appointments.",
"max_duration_seconds": 300
}'
MCP Server (for AI agent integration)
dograh mcp --port 8090
Common Pitfalls
- Latency: First response may be slow (LLM cold start). Use streaming for real-time feel.
- Telephony costs: Self-hosting eliminates platform fees, but you still pay Twilio/Vonage per minute.
- Voice quality: Test with your target TTS provider — some voices sound robotic at speed.
- Concurrent calls: Default config handles ~10 concurrent calls. Scale workers for more.
- MCP auth: When exposing MCP server, add authentication for production use.
Verification
dograh serve --port 8080 &
curl http://localhost:8080/health
curl -X POST http://localhost:8080/api/workflows \
-H "Content-Type: application/json" \
-d '{"name": "test", "voice": "alloy", "llm": "gpt-4", "prompt": "Say hello"}'
curl http://localhost:8080/api/workflows