What a guest actually does
- Opens the invite link (or types the room code on the home page).
- Gets a device check: pick camera, microphone, and speaker, see their own preview, and confirm the mic is picking up sound before they go in.
- Ticks the “this meeting may be recorded” box, so nobody is recorded without being told.
- Clicks Join. If the host runs a waiting room, they wait to be admitted; otherwise they are in.
That is the whole flow. The video and audio run over WebRTC through LiveKit, which is built into current Chrome, Edge, Firefox, and Safari, so there is nothing to install.
What is in the room
- Video and audio, screen share, whiteboard, reactions
- Waiting room, room lock, and host admit
- Live captions (Deepgram)
- Recording at HD 720p: one continuous file, MP4 in Chrome, Edge, and Safari, WebM in Firefox. Everyone sees a recording badge.
- Calendar invite (.ics) from the host console
Honest comparison
| Quantlys Meeting | Typical big-suite meeting app | |
|---|---|---|
| Guest install | None: browser tab only | Usually a web client exists, but the app is often pushed |
| Guest account | Not needed (a name is enough) | Varies by product and org policy |
| Large webinars, phone dial-in, rooms hardware | Not offered | Yes, and that is where they are strong |
| After the call | A markdown PRD or a Memory package | Recording, transcript, AI summary |
| Source code | MIT, on GitHub | Closed |
If you need a 500-person webinar or phone dial-in, use the big suites. Quantlys is for small working sessions where the link should just work and the call should end with something you can ship.
Who turns guest access off
Guest join is on by default. If you self-host, one environment flag (ALLOW_GUEST_JOIN=false) requires everyone to sign in. The waiting room and lock still apply on top when guests are allowed.
Related
- Open-source Zoom alternative: what you get and give up
- Podcast recording in the browser
- AI meeting assistant that writes the PRD