OpenCallIntroduction
What OpenCall is, and what you need to provision to put it online.
To follow the steps by hand, every page is a clickable dashboard-by-dashboard guide. To have an AI provision everything through a CLI, paste the AI runbook into a session — it assumes you already picked between LiveKit Cloud and self-host.
OpenCall is a community voice, video and chat product — a Discord of your own, simpler, that you host. Discord login, voice channels with video and screen sharing, text chat, and an admin panel to manage who gets access.
No step in this documentation touches code — it is all infrastructure.
Order to follow
Requirements → GitHub fork → Set up Discord → LiveKit (Cloud or self-host) → Attachment storage → Database → Production deploy (Railway) → Final check.
Pieces you are going to provision
| Piece | What it is for | Where |
|---|---|---|
| Discord app | User login (OAuth) | Set up Discord |
| Postgres | Users, messages, configuration | Database |
| LiveKit | Voice/video server (WebRTC) | Cloud or self-host |
| Object storage | Chat images (optional) | Attachment storage |
| Next.js hosting | The app itself (front + back) | Production deploy (Railway) |
There is a zero-cost path, with no credit card and no domain of your own: Demo deploy (Render) — Render + Neon + LiveKit Cloud. The ceiling is 5 people in a call at the same time.