Inspect and configure
Review agent configuration, knowledge retrieval, the LiveKit worker, telephony binding, and call records in the repository. Configure the providers and approved knowledge for your pilot.
MIT licensed · Open source
Your voice workflow. Source you can inspect.
Evaluate an open-source AI phone-agent stack with a customer console, API, voice runtime, and development tooling in one repository. Review the implementation and assign an operating owner before deciding how to run it.
Read the documentationDecide what your team wants to own.
Source access is useful when your team needs to inspect or change how calls, tools, and data are handled. It does not remove the work of integration, testing, monitoring, or responding to callers.
Implement and verify
Define each permitted calendar, CRM, or helpdesk operation. Test authentication, duplicate requests, failed writes, and human handoffs against the actual destination system.
Operate and review
Assign responsibility for hosting, secrets, access, retention, provider bills, incident response, and staff follow-up. If nobody can own this work, a managed alternative may fit better.
Compare the Vapi alternatives and Retell alternatives guides, then review hosted pricing and self-hosting costs with your technical evaluator. Use the pilot checklist and cost worksheet to record your assumptions before booking a demo.
Repository map
Follow the path from configuration to call.
apps/webProduct website
Next.js product pages, use cases, industry pages, blog content, pricing, and legal pages.
apps/consoleCustomer console
Organizations, agents, phone numbers, calls, knowledge bases, API keys, billing, and settings.
apps/serverControl plane
Express API for authentication, permissions, agent configuration, call workflows, providers, and retention jobs.
apps/aiVoice runtime
Python API and LiveKit workers for runtime configuration, retrieval, tools, privacy controls, and voice-agent execution.
Local quickstart
Start with a development environment.
With Docker, Docker Compose, Go Task, Node.js, and Python 3 available, the task runner prepares development environment files, dependencies, databases, migrations, and local services.
Real calls still require your configured voice, model, and carrier providers. Review the full setup notes before running the commands.
Read the setup notesTerminal
git clone https://github.com/allgpt-co/QuickVoice.git
cd QuickVoice
task up:dev- Console
- http://localhost:3000
- Website
- http://localhost:3001
- API docs
- http://localhost:5000/api/v1/docs
- AI health
- http://localhost:5555/health
Deployment requirements
Connect the services your workflow needs.
Local development
Generated development environment files
The task runner starts the local product services, Postgres, and Redis. Included database values are development-only placeholders.
Voice sessions
LiveKit and configured speech or model providers
Live voice uses credentials supplied by the operator for the selected runtime providers.
Carrier calls
Twilio or Telnyx, plus LiveKit
A fresh clone does not place real phone calls until carrier and LiveKit credentials are configured.
Optional services
Stripe, OAuth, SMTP, and S3-compatible storage
These credentials are needed only for the corresponding billing, sign-in, email, and object-storage paths.
License
MIT licensed, with terms you can read.
The MIT license permits use, modification, distribution, and commercial use, subject to retaining the copyright and permission notice. The software is supplied without warranty. Read the repository license for the full terms.
Read the MIT licenseReview your deployment before production.
Review authentication, secrets, storage, call data, recordings, transcripts, retention, and provider agreements for your environment. Source access does not certify a deployment or replace operational and compliance review.
For builders
Explore, contribute, and follow the project.
Repository
Inspect the source and project history.
DocumentationRead architecture, operations, and positioning notes.
ContributingReview the contribution workflow before opening a pull request.
IssuesReport a bug or propose a scoped improvement.
DiscussionsJoin project conversations on GitHub.
ReleasesFollow published versions and release notes.
Prefer the hosted console? Create an account and review your available wallet credit before testing.
Connect the source to your business workflow.
Bring your call requirements and technical questions to a demo, or send the team a written enquiry.