Skip to main content

MIT licensed · Open source

Your voice workflow. Source you can inspect.

QuickVoice brings a customer console, API, voice runtime, and development tooling into one repository. Review the implementation before deciding how to operate it.

Read the documentation

Repository map

Follow the path from configuration to call.

apps/web

Product website

Next.js product pages, use cases, industry pages, blog content, pricing, and legal pages.

apps/console

Customer console

Organizations, agents, phone numbers, calls, knowledge bases, API keys, billing, and settings.

apps/server

Control plane

Express API for authentication, permissions, agent configuration, call workflows, providers, and retention jobs.

apps/ai

Voice 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 notes
Terminal
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 license

Review 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.

Connect the source to your business workflow.

Bring your call requirements and technical questions to a demo, or send the team a written enquiry.