SMF·WHEREBY
Can a prompt replace Whereby?
Video meetings & webinars — permanent meeting rooms
Exhibit tracking slip
Verdict
Whereby's product is that the link always works: no download, no account for guests, no "can you hear me". Delivering that reliably means media servers and relays near your participants, which is infrastructure rather than code, so the verdict is no. The piece worth building is the front door — a permanent, memorable room URL with access rules a stranger cannot talk their way past — which is a sitting on top of conferencing software you run.
Exhibit A — The prompt
Received on31.07.2026Build the front door for meeting rooms you host: permanent URLs and access rules that actually hold.
Stack: a self-hosted conferencing server (LiveKit or Jitsi as the reference, with a TURN server, which is mandatory rather than optional), plus a small application on your own domain that owns rooms, tokens and access.
Rooms: permanent, named, at yourdomain.tld/room-name. Names are chosen but validated — reject anything short, sequential or guessable, and reserve a list of obvious words. An open room at a predictable URL is how strangers end up in your call.
Access modes per room, enforced when the join token is minted on the server, never in the client:
- **Open**: anyone with the link joins.
- **Lobby**: participants wait until an owner admits them, seeing a page that says so.
- **Knock**: like lobby, but the owner gets a notification with the knocker's stated name and can admit or refuse, with refusals remembered for that session.
- **Members only**: a signed-in allowlist.
The join token is short-lived, single-use and bound to the room. Write the test that a token for room A cannot join room B, and that an expired token is refused.
Room page before joining: a device check that confirms camera, microphone and network before the participant is in front of anyone, showing a simple pass or fail with what to do about a failure. This is a small feature that removes most of the awkwardness at the start of a call.
Owner controls: lock the room, mute a participant, remove a participant with a block for that session, and end the meeting for everyone. All server-enforced.
Operations: a health endpoint that verifies the TURN server actually relays media rather than merely responding, an alert when it fails, and a README section stating the measured participant limit for your hardware and the bandwidth per participant.
Write tests for token scoping and expiry, for lobby admission being server-side, and for the room-name validator rejecting sequential and short names.
Do not build recording, mobile apps, or a scheduling system.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the media infrastructure that makes a call hold up
- B.2 the mobile apps and browser tuning across every device
- B.3 recording with storage that scales
- B.4 custom subdomains and branded rooms
- B.5 somebody to call when a client cannot join
Prior art
Exhibit C — Why people still pay: media infrastructure
Because "the link just works, for anyone, on any device" is a promise you can only keep with servers in enough places, and eleven dollars a month is a small price for never troubleshooting a guest's browser.
Questions
Why enforce access when the token is minted rather than in the UI?
Because anything enforced in the client is a suggestion. The server decides whether to issue a join token, and that single choice makes lobby and knock real rather than decorative.
Is a pre-join device check worth building?
It is one of the highest-value small features in conferencing. Catching a muted microphone before the participant is on camera in front of five people removes the most common two minutes of every call.
How many people can a self-hosted room hold?
It depends on your uplink and CPU, which is why the prompt asks you to measure and publish the number. Small team calls are comfortable on modest hardware; the hundred-attendee promise on a paid plan is bought capacity, not clever code.
Why does the price citation point at a different URL?
Because whereby.com/pricing is not a pricing page — Whereby turns any unrecognised path into a meeting room, so that URL opens a room called "pricing". The real page is under /information/meetings/pricing, which is what this entry cites.
Related tools
Receipt