Scheduling and meetings decision
Whereby
A competent developer can build a usable browser-based conferencing replacement (embedding, rooms, chat, recordings) but reproducing Whereby’s certified compliance, globally distributed server mesh, uptime SLA, and enterprise support is expensive and time-consuming, so paying is reasonable for production-critical or enterprise use.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
Code Whereby publishes itself
Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.
What a replacement has to do
- Start/join browser WebRTC calls, host rooms with persistent URLs, share video/audio/screen/chat, optionally record and transcribe sessions.
What it still won’t have
- Globally distributed server mesh and bandwidth-optimized routing across regions
- Enterprise SLAs (99.9% uptime) and large-scale reliability guarantees
- Official compliance certifications (GDPR/HIPAA configuration and ISO 27001 certification)
- Mobile SDKs and embeddable pre-built UI with maintained docs and developer support
- Dedicated customer success and enterprise-level support included
What remains hard
- Compliance and regulation
Built in Europe, our products are GDPR and HIPAA compliant, and ISO 27001 certified.
- Infrastructure at scale
Globally distributed server mesh
- Execution quality
Unrivaled support From our developer docs to our dedicated Success team, we’re here to help. At no extra cost.
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 21 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted WebRTC conferencing service using React for the web UI, Node.js + Express for signaling, Janus or mediasoup as the SFU, Coturn for TURN/STUN, Postgres for room metadata, and S3-compatible storage for recordings. In scope: persistent room URLs, join/create UI, basic in-call controls (mute/camera/screenshare/chat), server-side cloud recording saved to S3, and optional speech-to-text via a third-party API. Out of scope: achieving ISO 27001/HIPAA certification, multi-region global mesh, mobile native SDKs, and enterprise SLA. Include authentication for locked rooms, webhooks for events, error handling, and automated unit/integration tests for signaling and recording flows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- Price verified on pricing page+3
- Hard moats found in the evidence-6
- Evidence score57
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productWhereby (product)
- official pricingWhereby pricing
- official docsWhereby features
- open sourcemirotalk (repo)
- official pricingWhereby pricing
Integrity checks
What held up, and what did not.
