QuantlysWhat you run, and what still leaves
- The app: a Next.js app on Vercel or any Node 22+ host.
- Media: LiveKit Cloud, or your own
livekit-serverso audio and video stay off LiveKit Cloud. - Data: Supabase for host sign-in, meeting history and row-level security, plus an S3-compatible bucket (R2, S3, MinIO).
- Captions: Deepgram, on your key. Speech goes to Deepgram.
- Writers: OpenAI or OpenRouter, on your key, for notes, the PRD and Memory mode. Transcripts go to that provider.
- Email (optional): Resend for invites, digests and emailing the spec.
So self-hosting the media server keeps media on your servers, but not the words. The self-host guide says the same thing, and lists what a bare SFU doesn't include, like recording egress.
What Zoom does better
- Reliability at scale, including webinars for up to 100,000 attendees.
- Phone dial-in, room systems, and desktop and mobile apps.
- Enterprise admin with SAML and OIDC SSO.
- Nothing to operate. With Quantlys Meeting, upgrades, keys and uptime are your job.
If you want a general-purpose self-hosted meeting server, also look at Jitsi Meet and BigBlueButton. My older open-source Zoom alternative page compares them.
Side by side
How I compared. Quantlys Meeting rows come from the public source code and README (v1.1.3). Zoom rows were checked on each vendor's own website or help center on Oct 19, 2026 (as of Oct 2026); every cell links to the page it came from. ✗ means the vendor's own page says it isn't offered. “Not listed on their site” means I couldn't find it on their official pages, not that it doesn't exist. Plans and features change, so check the vendor before you decide.
| Quantlys Meeting (self-hosted) | Zoom | |
|---|---|---|
| Source code license | ✓ MIT | Not listed on their site |
| Run the app on your own infrastructure | ✓ Vercel or any Node 22+ host | Not listed on their site |
| Run your own media server | ✓ Your own LiveKit SFU, or LiveKit Cloud | Not listed on their site |
| Recordings in your own storage | Partial: Supabase Storage / S3-compatible bucket; a bare SFU needs extra pieces | Not listed on their site |
| White-label (your domain, your brand) | ✓ Allowed under MIT | Not listed on their site |
| Guests join in a browser with no account | ✓ On by default; can require sign-in | ✓ Zoom Web App |
| Waiting room, lock, host admit | ✓ | ✓ |
| Recording retention you control | ✓ RECORDING_RETENTION_DAYS nightly job | Not listed on their site |
| Live captions | ✓ Deepgram, your key | ✓ Translated captions |
| Meeting that writes a PRD | ✓ | Not listed on their site |
| Phone dial-in | ✗ | ✓ |
| Webinars | ✗ | ✓ Up to 100,000 attendees |
| SSO | ✗ Optional single email-domain limit for hosts | ✓ SAML / OIDC |
| Who runs it | You: upgrades, keys, uptime | Zoom |
Ten-minute local start
git clone the repo, copy .env.example to .env.local, fill in your keys, run the Supabase schema, then npm install and npm run dev. Open /host, start a meeting and open the guest link in a second tab. The full checklist is on self-hosted video conferencing.
Getting the PRD into your tools
The PRD panel has an Export menu with these options, no setup needed:
- Copy as Markdown or Download .md.
- New GitHub issue: a prefilled create-issue link for the repo you type (owner/repo).
- New Linear issue: a prefilled create-issue link.
- Jira and Notion: copies the markdown and opens Jira's create dialog on your atlassian.net site, or a new Notion page, so you can paste it.
A PRD too long for a link is cut at a line, with a link back to the full PRD. You can still paste the markdown into Quantlys Conclave by hand.
Direct push. You can also push the PRD straight into GitHub Issues, Linear, Jira or Notion. You connect your own token for each tool; it's stored encrypted and only its last 4 characters are shown again. You see a preview of exactly what will be created before anything is sent.
- GitHub Issues: one PRD issue plus one issue per user story, with acceptance criteria as a checklist. Stories are linked as sub-issues where the repo supports it.
- Linear: one PRD issue with a sub-issue per user story, criteria as a checklist.
- Jira Cloud: the PRD as an Epic with each user story as a Story under it (unlinked Stories if the project has no Epic type).
- Notion: one page under a parent page you pick, with criteria as to-dos.
Re-pushing updates the items it made last time instead of duplicating them. In Notion it writes a fresh page and moves the old one to the trash. Self-hosting? Direct push needs an encryption key and a database migration; see docs/INTEGRATIONS.md.
FAQ
Is Quantlys Meeting fully self-hosted?
You run the app and can run your own LiveKit media server. Captions still go to Deepgram and the PRD and notes writers to OpenAI or OpenRouter, on keys you hold, so the words do leave your servers.
What do I need to self-host it?
A Node 22+ host such as Vercel, plus LiveKit (Cloud or your own server), Supabase, S3-compatible storage, Deepgram and an OpenAI or OpenRouter key. Resend is optional for email. The quickstart is in the README.
Does recording work on a bare LiveKit server?
Not out of the box. The self-host guide lists the extra pieces a single livekit-server binary does not include, so read docs/SELF_HOST.md before relying on recording.
Is it a full replacement for Zoom?
No. It has no phone dial-in, webinars, room systems, native apps or SSO. It is built for small working sessions, especially spec meetings that should end in a PRD.
What does it cost?
The code is free under the MIT license. You pay LiveKit, Deepgram, Supabase, your storage provider and your model provider directly at their prices.
Go deeper
- Example PRD: a labeled specimen of what the room writes (not a customer recording).
- PRD from a meeting: how recorded sessions on a project become one markdown spec.
- Open-source video conferencing: the MIT repo and the keys you bring.
- Source: github.com/SantoshA1/quantlys-meet (MIT)
- Built by Santosh Adari on Quantlys.
Zoom, Otter, Granola and Fireflies are trademarks of their respective owners. Quantlys Meeting is not affiliated with, sponsored by, or endorsed by them. Competitor details were checked on their official sites on Oct 19, 2026 and may have changed since. Spot something wrong or out of date? Email admin@agilityserv.com and I'll fix it.