Chatty by PersonaliAI

Open-source AI customer support: chat widget + real-time voice agent, grounded in your own knowledge base.

Self-host it in five minutes with Docker, or let us run it for you. No vendor lock-in either way — the hosted version and this repo are the same code.

Chatty Cloud (hosted) · Documentation · Quick Start · Features · Architecture · Contributing

---

Why Chatty

Every hosted chatbot SaaS charges per-seat or per-message and holds your conversation data. Chatty is open-core: run it yourself for free, or use Chatty Cloud — our own hosted version of this exact repo, if you'd rather skip the ops work. Either way you get the same feature set — streaming chat, a real-time voice agent, RAG over your own documents, meeting booking, lead capture, WhatsApp/Slack/Telegram channels.

	Closed-source SaaS chatbots	Chatty
Your conversation data	Lives on their servers, always	Your Supabase project — whether you self-host or use Chatty Cloud
Pricing	Per-seat / per-message, no free tier	Self-host for free, or a straightforward hosted plan on Chatty Cloud
LLM	Locked to their model	Bring your own — Gemini by default, or BYOK OpenAI/Anthropic/OpenRouter
Voice agent	Usually a separate, pricier tier	Included, same knowledge base as chat
Source code	Closed	MIT licensed — fork it, audit it, extend it, run it anywhere

✨ Features

• 💬 Embeddable chat widget — one <script> tag, streaming replies, works on any website
• 🎙️ Real-time voice agent — phone-call-style conversations via LiveKit, same brain as the chat widget
• 📚 RAG over your own knowledge base — upload PDF/DOCX/PPTX/XLSX, crawl URLs, auto-chunked and embedded
• 🛠️ Tool-calling — books real meetings (Zoom/Google Meet links), captures leads, checks a calendar
• 🔌 Omnichannel — WhatsApp, Slack, and Telegram, in addition to the web widget
• 🔑 BYOK — default is Gemini (generous free tier); swap in your own OpenAI/Anthropic/OpenRouter key per bot
• 📊 Dashboard — manage bots, inbox/conversations, knowledge sources, booking rules, and channel connections
• 🐳 One-command self-host — docker compose up, point it at a free Supabase project, done

🏗️ Architecture

flowchart LR
    visitor(("Website visitor")) -->|chat / voice| widget["Embeddable widget\n(Next.js)"]
    owner(("Bot owner")) --> dashboard["Dashboard\n(Next.js)"]
    widget --> api["chatty-backend\n(FastAPI)"]
    dashboard --> api
    caller(("Phone-call-style\nvoice visitor")) -->|WebRTC| voice["voice_worker.py\n(LiveKit Agents)"]
    voice --> api
    api --> db[("Supabase\nPostgres + pgvector + RLS")]
    api --> llm["Gemini / BYOK LLM"]
    voice --> livekit["LiveKit Cloud\n(WebRTC transport)"]

    style widget fill:#6366f1,color:#fff,stroke:none
    style dashboard fill:#6366f1,color:#fff,stroke:none
    style api fill:#009688,color:#fff,stroke:none
    style voice fill:#ff6600,color:#fff,stroke:none
    style db fill:#3ecf8e,color:#000,stroke:none

Loading

chatty/
├── frontend/     Next.js — dashboard, embeddable widget, widget.js loader
├── backend/      FastAPI — chat/RAG/bookings/channels API
│   └── voice_worker.py   a separate LiveKit Agents process for the voice agent
└── docker-compose.yml

Both services talk to a single Supabase Postgres database — schema + row-level security policies, no separate ORM. Supabase's free tier is enough to get started.

🚀 Quick Start (Docker Compose)

1. Create a Supabase project at supabase.com — free tier is fine. Grab these from Project Settings → API and → Database:

• Project URL, anon key, service_role key
• Database host/password (for the direct Postgres connection)

2. Apply the database schema:

cd backend
pip install psycopg2-binary
python scripts/apply_migrations.py "postgresql://postgres:YOUR_PASSWORD@YOUR_HOST:5432/postgres"

3. Configure environment variables:

cp backend/.env.example backend/.env        # fill in Supabase + Gemini keys
cp frontend/.env.example frontend/.env      # fill in Supabase URL + anon key
cp .env.example .env                        # same NEXT_PUBLIC_* values (used at Docker build time)

At minimum you need: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, GEMINI_API_KEY (free at aistudio.google.com/apikey), FUNCTION_SECRET and BYOK_ENCRYPTION_KEY (generate with the commands in backend/.env.example). Everything else is optional — each unlocks one feature (voice, WhatsApp, Slack, billing, etc.) and can be left blank.

4. Run it:

docker compose up --build backend frontend

Dashboard: http://localhost:3000 — sign up, create a bot, and the widget embed snippet is generated for you under bot settings.

To also run the voice agent: docker compose up --build (no service names) brings up voice-worker too. It needs a free LiveKit Cloud project — set LIVEKIT_URL, LIVEKIT_API_KEY, LIVEKIT_API_SECRET in backend/.env.

💻 Local Development (without Docker)

Backend:

cd backend
python -m venv .venv && .venv\Scripts\activate   # or source .venv/bin/activate on macOS/Linux
pip install -r requirements.txt
uvicorn main:app --reload --port 8000

Frontend:

cd frontend
npm install
npm run dev

Voice worker (optional):

cd backend
python voice_worker.py dev

⚙️ Configuration Reference

Every environment variable is documented inline in backend/.env.example and frontend/.env.example — what it's for, where to get it, and what happens if you leave it blank.

🗺️ Roadmap

• One-click deploy buttons (Railway / Render / Fly.io)
• Additional channels (Instagram DM, Discord)
• Multi-language knowledge base auto-translation
• Admin CLI for bulk bot provisioning

Have an idea? Open an issue.

🤝 Contributing

Issues and PRs welcome — this is a young project and there are rough edges. Good first areas: additional STT/TTS provider plugins, additional channel integrations, docs.

📄 License

MIT — see LICENSE. Use it, fork it, ship it commercially — attribution appreciated but not required.

---

If Chatty is useful to you, star the repo ⭐ — it helps other people find it.