Whereby alternatives: 3 options compared
Compare recorded free and open-source options, their capabilities and operating requirements. Source dates are shown below; licenses, hosted limits and project activity can change.
what to keep, change or build
People still pay for Whereby because video products survive because real-time media quality and global reliability are infrastructure businesses, not weekend interface projects. The recurring cost buys TURN capacity, codecs, browsers, packet loss, scaling, recording, consent, abuse, monitoring, and incident response, not just the visible interface.
- Business requires at least 3 paid hosts, making its monthly minimum $41.97. Prices exclude VAT.
- A narrower workflow may be enough: small private meeting service.
- Check the existing free tier before switching: 1 host, 1 room URL, 4 attendees, 30 minutes per meeting and 4 active video feeds
The scoped build: Host one simple private browser meeting room on a self-managed WebRTC stack, issue signed room links, and keep recordings only when every participant is clearly informed. The guide does not recommend recreating the complete product. Evaluate an existing alternative or the smaller consolation scope.
Do not assume parity: browser media reliability, TURN capacity, recording, embeds, and support; global low-latency media network; dial-in and telephony; large webinars; transcription, support, and compliance.
Ongoing work: TURN capacity, codecs, browsers, packet loss, scaling, recording, consent, abuse, monitoring, and incident response.
Read the Whereby implementation scope, requirements and prompt →
shortlist by the workflow you need
Keep the workflow on your machine: Nextcloud Talk. Check operating-system support and data import before moving a local library.
Control the deployment: MiroTalk SFU, Nextcloud Talk. Include updates, backups and service operations in the decision.
Start with a managed service: Jitsi Meet. Check the current free tier, data export and paid feature boundaries.
Before asking AI to rebuild an alternative: compare its documented install, engine and storage requirements below. Extending an existing project may save implementation work when its license allows it; a desktop workflow or free hosted tier alone does not establish that the software is easy to recreate. Use the linked product details and build guide to check the smaller scope.
Click a room link and meet; no account choreography required.
scope checkTest moderation, recording, guest access and network quality against your meeting requirements.
official-source review 2026-10-26 · edition and cost details
A capable WebRTC room in one Docker stack, with lobby, whiteboard and recording.
licenseAGPL-3.0
runsyour machine or their cloud
installUse the public browser demo, or deploy the Ubuntu/Docker Compose stack with a domain, TLS, and exposed WebRTC ports
dataLive media is forwarded through the selected SFU and is not stored by default; optional recordings are WebM files in the configured recording directory or an S3-compatible bucket.
the catch vs WherebyMiroTalk can match the room features, but reliable public use means operating Docker, TLS, TURN, recording storage, updates, and browser compatibility yourself.
setupSelf-hosting requires a public Ubuntu server, DNS/TLS, Docker or Node.js, a wide TCP/UDP media-port range, and usually TURN; free AGPL use also does not include unrestricted rebranding.
recorded source check 2026-08-10 · installation not tested
Browser meeting links inside Nextcloud; scaling them turns into a TURN-server hobby.
licenseAGPL-3.0
runsyour server
installEnable the Talk app from the app store inside an existing Nextcloud server; add TURN and the High Performance Backend for harder networks or larger calls
enginesOptional Nextcloud Assistant backends provide transcription, translation, and summaries; ordinary chat and calls do not require an AI model.
dataMessages and call metadata live in the Nextcloud database, shared files live in the Nextcloud data store, and recordings/transcripts remain on the administrator's configured Nextcloud infrastructure.
the catch vs WherebyNextcloud Talk makes one simple room depend on a whole Nextcloud installation, and reliable group calls require a high-performance backend and TURN rather than Whereby's turnkey room.
setupThe apparent one-click install assumes a working Nextcloud server; reliable external calls then require TURN, while larger calls and webinars add the High Performance Backend and substantial networking work.
recorded source check 2026-08-10 · installation not tested
latest recorded source check 2026-08-10 · check current terms at the source
choose by workflow and operating requirements
Use the recorded scenario and feature gaps to choose a shortlist. Open-source code can still require hosting, storage, model APIs or paid services; a free tier can limit features.
| tool | license / edition | running it | platforms | stars | active |
|---|---|---|---|---|---|
| Jitsi Meet details | open source | they host it | web, ios, android | 29,700 | 2026-08 |
| MiroTalk SFU details | AGPL-3.0 | docker to self-host | web, self-hosted | 3,100 | 2026-08 |
| Nextcloud Talk details | AGPL-3.0 | self-host, real ops | web, macos, windows, linux, ios, android, self-hosted | 2,200 | 2026-08 |
People still pay for Whereby because video products survive because real-time media quality and global reliability are infrastructure businesses, not weekend interface projects. The recurring cost buys TURN capacity, codecs, browsers, packet loss, scaling, recording, consent, abuse, monitoring, and incident response, not just the visible interface. The recorded subscription totals $131.88 a year before any costs of an alternative.
Questions about these alternatives
Is there a free alternative to Whereby?
The catalogue lists Jitsi Meet, MiroTalk SFU, Nextcloud Talk. Compare the specific free edition, license, hosting costs and current availability before choosing; a listing does not promise that every feature is free.
Should I just build my own Whereby?
Our verdict is NOT REALLY. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Whereby, host one simple browser meeting room using a self-managed WebRTC stack. The hard boundary is browser media reliability, turn capacity, recording, embeds, and support, plus real-time media infrastructure and reliability. Review the scope, implementation prompt and trade-offs in the Whereby build guide.