Whereby
UK / wider Europe Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Whereby AS · whereby.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Whereby at a glance
- Vendor
- Whereby AS
- Headquarters
- Incorporated in Norway source, captured 16 Nov 2026
- Data hosting
- In the EU by default; pages mention Ireland source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Whereby 2.5/5, the mean of 6 judges. Whereby is a browser-first video conferencing product from Whereby AS of Norway, sold as Meetings, charged per user license, and Embedded, charged by usage. how scores are made
- As of
- Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Whereby is a browser-first video conferencing product from Whereby AS of Norway, sold as Meetings, charged per user license, and Embedded, charged by usage. The judges score it strongest on encryption and access: end-to-end encryption is offered for small rooms with the quality-and-stability trade-off named, DTLS-SRTP, TLS 1.2 and AES256 are stated, and the vendor says it cannot decrypt small-room content. The weakest area is pricing transparency: no per-user or per-host plan price appears, and the storage overage fee carries no figure, so an annual invoice is not computable from the pages. Meeting core rests on documented breakout groups (main room up to 200 people, up to 20 groups) and detailed screen-sharing and firewall pages, while we found no public information on host moderation, waiting rooms or a stated accessibility standard. Recording governance turns on recordings in the customer's own S3 bucket; sovereignty notes infrastructure mostly on AWS Dublin, account data in Ireland, usage information also hosted in the United States, and subprocessors published only as categories.
Speaks for it
- End-to-end encryption offered for small rooms with the quality-and-stability trade-off named and cryptography spelled out (DTLS-SRTP, TLS 1.2, AES256)
- Recordings can sit in the customer's own S3 bucket where Whereby stores nothing, deletable via the Recordings page or API
- A deeply documented REST API and SDK covering rooms, meetings, recordings, transcriptions and summaries, with webhooks and code examples in five languages
- Breakout groups documented concretely — main room up to 200 people, up to 20 groups, drag-and-drop or shuffle assignment
- Transcription processing runs through EU-based servers, and a Data Processing Agreement is linked from the documentation
Held against it
- No per-user or per-host plan price appears (only usage components such as live captions at $0.0065 per unmuted participant minute on the Build monthly plan), and the storage overage fee carries no figure
- We found no public information on host moderation such as mute-all or removing participants, on waiting rooms, or on per-plan participant limits
- We found no public information on SSO, SCIM provisioning, or calendar add-ins for Microsoft 365 or Google Workspace
- Live captions are in open beta on paid Embedded plans only and not available in the iOS app, and dial-in is closed beta for selected customers only
- Whereby states it would not delete your media files automatically, and collecting participants' consent is the customer's responsibility
Best for
- You are a product team embedding video calls into your own application and want a documented REST API, webhooks and SDK control over recordings
- You hold sensitive small-group meetings and want end-to-end encryption from a vendor that states it cannot decrypt small-room content
- Your data rules require recordings to land in your own S3 bucket rather than vendor storage
- You need guests to join from a browser on permanent room links with no install
Avoid if
- You must compute an annual invoice from public pages before committing — the pricing hub links to Meetings and Embedded pricing pages without per-user or per-host figures
- You rely on telephone dial-in for reach — it is in closed beta for selected customers only and not compatible with breakout groups
- Your retention rules require scheduled automatic deletion of stored recordings — Whereby states it would not delete your media files automatically
- Your compliance review requires subprocessors named with locations — the published disclosure stops at categories
The scores
| Criterion | Panel median |
|---|---|
| The meeting itself | 3 of 5 |
| Encryption & meeting access | 3.5 of 5 |
| Reach & accessibility | 3 of 5 |
| Recordings, retention & admin control | 2.5 of 5 |
| Integrations & deployment | 2.5 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 1.5 of 5 |
The meeting itself
Show reasoningHide reasoning
How this is scored
Whether the call works: participant capacity, video and audio quality under load, screen sharing, breakout rooms, moderation, and what happens on a bad connection.
0 — Not a meeting tool: no multi-party video calls, only one-to-one calls or recorded video.
3 — Video meetings with screen sharing, chat and host controls such as mute-all.
5 — Meetings with a stated participant limit per plan, screen sharing, breakout rooms or a waiting room, and host moderation (mute, remove, assign co-hosts).
8 — Large meetings and webinars with published capacity limits, per-participant moderation and waiting rooms, layout control, simulcast or adaptive bitrate stated, and behaviour on constrained or mobile networks documented.
10 — Scale and control are engineering claims the vendor stands behind: capacity published per plan and per region, selective forwarding with adaptive quality documented, live streaming, hardware-room support, and diagnostics an admin can read after a bad call.
The IT Administrator
Main-room capacity of 200 with up to 20 breakout groups is published rather than promised, and screen sharing is documented in real detail — frame rates, resolution caps and per-platform audio limitations — which is the kind of documentation I trust. What I found no public information on is host moderation such as mute-all or removing participants, waiting rooms, adaptive bitrate for video, and any diagnostic an admin can read after a bad call; the low-bandwidth capability is a homepage claim, not documented behaviour. 1 5 6
The Security Officer
Screen sharing, chat and breakout groups are documented, with a main room that holds up to 200 people split into as many as 20 groups, and the vendor even documents the degraded TURN-over-TCP path on locked-down networks. Host moderation is the hole: I found no public information on muting, removing participants or assigning co-hosts, and no waiting room; the 200-person capacity is stated for breakout groups rather than per plan. 1 5 6 7
The Works Council Advocate
The main room holds up to 200 people split into as many as 20 breakout groups with drag-and-drop or shuffle assignment, plus screen sharing up to 1080p, chat, file sharing and a virtual whiteboard. Behaviour under constrained networks is partly documented — the TCP/TLS relay fallback may reduce call quality — but we found no public information on waiting rooms, per-participant moderation such as mute-all or removing participants, or capacity limits stated per plan. 1 5 6 7
The Educator
Breakout groups are genuinely usable: the main room holds up to 200 people, splits into a maximum of 20 groups with drag-and-drop or shuffle assignment, and the vendor documents what happens on return (cameras off, microphones muted). Screen sharing is documented from the browser with tab, window and full-screen options, and constrained networks get real treatment — a TURN relay on port 443 with a TCP/TLS fallback where the vendor itself says 'call quality may be reduced compared to UDP', plus a claim of consistent quality 'including in low bandwidth scenarios and on mobile devices'. We found no public information on waiting rooms, per-participant host moderation such as mute-all or removal, or capacity limits per plan. 6 5 7 1
The Accessibility Advocate
Breakout groups are documented with a 200-person main room, up to 20 groups and host-managed assignment, alongside unusually detailed screen sharing and a global TURN relay network whose TCP fallback names its quality cost. We found no public information on waiting rooms, per-plan participant limits, or host moderation such as mute-all, remove or co-hosts, which caps this below the mid band. 1 5 6 7
The Skeptic
The main room holds up to 200 people, splittable into up to 20 breakout groups with drag-and-drop or shuffled assignment, and returning participants default to cameras off and microphones muted; screen sharing is documented down to frame rate (1–5 FPS default, up to 1080p) with platform-by-platform audio limits. Firewall documentation names the constrained-network behaviour: UDP preferred, TURN over TCP/TLS as a fallback where call quality may be reduced. We found no public information on host moderation such as mute-all, removal or co-host assignment, on waiting rooms, or on participant limits stated per plan. 1 5 6 7
Encryption & meeting access
Show reasoningHide reasoning
How this is scored
What is actually encrypted and against whom, plus who can get into a meeting. Judged on documented mechanism rather than on the word "encrypted".
0 — The vendor states that meeting media is transmitted unencrypted.
3 — Encryption in transit stated, with meetings protected by a link or passcode.
5 — Encryption in transit and at rest stated with the method named (for example TLS and AES), a lobby or waiting room with host-controlled admission, and meeting passcodes or locking.
8 — Optional end-to-end encryption for meetings with the trade-offs named (which features stop working), documented key handling, SSO-gated joining, and per-meeting access policies.
10 — End-to-end encryption available without surrendering the product — its cryptography documented or open source, key management explained, identity verification for participants, and the vendor stating plainly what it can and cannot see.
The IT Administrator
The mechanism is written down rather than waved at: DTLS-SRTP with client-generated keys, AES256 at rest, TLS 1.2 only, TURN relays that do not break encryption, and an end-to-end small-meeting mode whose quality trade-off is named, with large rooms described plainly as decrypted in server memory for routing and never persisted. Key storage in AWS Ireland is stated and the vendor says it cannot decrypt small-room content. I found no public information on SSO-gated joining or participant identity verification, which is exactly where board-meeting access control would live. 3 4 8
The Security Officer
Small rooms get genuine end-to-end encryption with client-generated DTLS-SRTP keys, and the vendor is unusually plain that it cannot decrypt that content and that large-room media is decrypted only in server memory for routing. Key handling is only partly explained — one captured page describes client-generated keys, another states keys are stored within AWS in Ireland — and the trade-off is named as quality and stability. I found no public information on meeting passcodes, locking or a lobby, so the question of who can walk in with a link goes unanswered on these pages. 3 4 8
The Works Council Advocate
Encryption in transit and at rest is stated with the methods named (TLS 1.2, AES256, DTLS-SRTP for media), and a small-meeting mode offers end-to-end encryption with the trade-off named — quality and stability — using client-generated keys, while large rooms are decrypted only in server memory for routing and never persisted. Time-limited access links with configurable expiry give per-meeting access control, but we found no public information on a lobby or waiting room, meeting locking, or SSO-gated joining. 3 4 8 11
The Educator
End-to-end encryption is offered honestly: a 'Small meeting' mode uses client-generated DTLS-SRTP keys with keys stored in AWS in Ireland, the vendor states plainly it 'cannot decrypt meeting content' in that mode, and the trade-off is named — prioritising encryption 'over quality and stability'; large rooms are decrypted only in server memory for routing and never persisted. In transit it is TLS 1.2, at rest AES256, and unencrypted modes are stated as unsupported. We found no public information on a lobby or waiting room, meeting passcodes or locking, or SSO-gated joining, so admission control rests on the customer's own application. 8 4 3
The Accessibility Advocate
End-to-end encryption is offered for small rooms with the trade-off named (quality and stability), the cryptography is named (DTLS-SRTP, client-generated keys, TLS 1.2, AES-256 at rest), and the vendor states plainly what it can see for each room size. The meeting-access half is thin: we found no public information on a lobby with host-controlled admission, meeting passcodes, locking or SSO-gated joining. 3 4 8 13
The Skeptic
The security pages give the sentence a buyer should demand: small meeting mode carries end-to-end encryption with the trade-off named — quality and stability — while in large rooms media is decrypted only in server memory for routing and never persisted, and Whereby states it cannot decrypt small-room content. Methods are named throughout (TLS 1.2 in transit, AES256 at rest, DTLS-SRTP for media), no unencrypted mode is supported, and TURN relaying preserves encryption. We found no public information on meeting passcodes, locking, a lobby with host-controlled admission, or SSO-gated joining. 3 4 8
Reach & accessibility
Show reasoningHide reasoning
How this is scored
Whether everyone who needs to join can: browser without an install, dial-in, low bandwidth, guests without accounts, captions and keyboard operation.
0 — Joining requires an installed client and an account; guests cannot take part.
3 — Guests join by link, through an app or the browser.
5 — Browser joining without an install, guest access by link without an account, mobile apps for iOS and Android, and either telephone dial-in or live captions.
8 — Telephone dial-in with numbers listed per country, live captions, a keyboard-navigable and screen-reader-tested interface or a stated accessibility standard (WCAG, BITV), and documented low-bandwidth behaviour.
10 — Reach is designed for: browser parity with the client, dial-in across the regions the customer operates in, live captions and translation, a published accessibility conformance report, and a usable experience on a poor mobile connection.
The IT Administrator
Browser joining without an install is the product's whole design, guests join on permanent room links, and live captions cover 32 languages. Both reach extras are betas, though — dial-in is closed to selected customers and incompatible with breakout groups, captions are open beta and not available in the iOS app — and I found no public information on a stated accessibility standard, keyboard or screen-reader testing, or dial-in numbers listed per country. 1 5 9 10
The Security Officer
Browser joining is real — local recordings even stay in the user's browser — and live captions cover 32 languages, but they sit in open beta, only on paid Embedded plans, and are not available in the iOS app; telephone dial-in is closed beta for selected customers only. We found no public information on Android apps, keyboard and screen-reader operation, or any stated accessibility standard. 4 9 10
The Works Council Advocate
Joining is browser-based by design with permanent room links for guests, and live captions are offered in 32 languages — currently an open beta on paid plans and absent from the iOS app. Telephone dial-in with numbers from different countries exists only in a closed beta for selected customers, and we found no public information on an accessibility standard, conformance report, or keyboard and screen-reader testing. 1 7 9 10
The Educator
Captions cover 32 languages including German, but they are in open beta, a supplementary feature of paid Embedded plans only, and stated as unavailable in the Whereby iOS app; dial-in exists with numbers from different countries, yet it is in closed beta for selected customers and stated as not compatible with breakout groups — thin comfort for someone in a dead spot. Joining is browser-first (screen sharing is documented from Chrome/Chromium, signalling runs outbound over port 443 only), and the vendor claims consistent quality including in low bandwidth scenarios and on mobile devices, though screen sharing on mobile is stated as not currently available. We found no public information on a stated accessibility standard or keyboard and screen-reader testing. 10 9 1 5
The Accessibility Advocate
Live captions exist in 32 languages but sit in open beta, only on paid plans, are absent from the iOS app, and are priced per unmuted participant minute; dial-in is a closed beta for selected customers with numbers delivered per meeting rather than published per country. Decisively, we found no public information on keyboard operation, screen-reader testing, a stated accessibility standard, or a published conformance report — without a report the accessibility story is marketing — so browser joining, a low-bandwidth claim and the documented constrained-network fallback carry the score no further. 9 10 1 5 7
The Skeptic
Joining runs in the browser — the screen-sharing pages are written around Chrome tabs and local browser storage — and registration is optional, so guests join by permanent room link. Live captions span 32 languages but sit in open beta on paid Embedded plans and are not available in the iOS app; dial-in is in closed beta for selected customers only, with numbers "from different countries" and no per-country list. We found no public information on an Android app, keyboard navigation, screen-reader testing or any stated accessibility standard. 3 5 9 10
Recordings, retention & admin control
Show reasoningHide reasoning
How this is scored
A recording is personal data about everyone in the room. Who may record, who is told, where it is stored, how long it lives, and what the works council can switch off under BetrVG §87(1) no. 6.
0 — The vendor states that any participant can record without notice to the others, with no admin control.
3 — Recording limited to the host or set by the organiser, with participants notified that the meeting is recorded.
5 — An admin setting for who may record, participants notified or asked for consent when recording starts, recordings stored in a stated location (cloud region or local), and deletion of recordings by host or admin.
8 — Automatic retention and deletion per policy, recordings encrypted at rest with access logged, transcription and AI summaries handled with their own switch and retention rule, and attendance or analytics features that can be switched off for co-determination.
10 — Built for a works agreement: every recording, transcript and analytics feature independently switchable and documented, retention executed and evidenced, an audit trail of who accessed which recording, and participant-level behavioural scoring stated as not part of the product.
The IT Administrator
Recording triggers are configurable per room or from the dashboard, cloud recording is an Embedded-plan feature with my own S3 bucket as an option where the vendor stores nothing, and deletion runs from the Recordings page or the API. But Whereby-provided storage is never deleted automatically, consent collection is explicitly the customer's responsibility rather than a built-in notice, and I found no public information on access logging for recordings or retention rules for transcriptions. 3 8 12
The Security Officer
Recording is customer-controlled — auto-start on one or two joiners, host prompt, or manual — with recordings stored either in the customer's own S3 bucket, where the vendor stores nothing, or in paid vendor storage, and deletion available through the Recordings page or API. Participant notice is explicitly the customer's responsibility, and the vendor itself states it would not delete your media files automatically, so retention stays entirely in the customer's hands. 3 12
The Works Council Advocate
Recording is configured in the dashboard or per room via the API with selectable triggers, recordings can be sent entirely to the customer's own S3 bucket so the vendor stores nothing, and deletion is available through the recordings page or API — real levers for a works agreement. But the vendor states plainly that it does not automatically delete media in its own storage, collecting participants' consent is made the customer's responsibility with no in-product notice mechanism evidenced, and we found no public information on access logging for recordings or on switching off attendance or analytics features. 3 4 12
The Educator
Recordings go where the customer chooses — own S3 bucket, or opt-in Whereby-provided storage — and can be deleted or downloaded through the portal or the API; the Meetings product offers local recording only, stored on the user's device with no Whereby access. Consent is placed squarely on the customer, who is 'responsible for collecting consents from all participants in the meeting prior to starting the recording'. Whereby states it 'would not delete your media files automatically' — the opposite of the scheduled retention a works council wants — and we found no public information on access logging for stored recordings, though caption and transcription behaviour is configurable globally or per room and chat is never stored beyond the meeting. 12 3 8 4
The Accessibility Advocate
Recording triggers are configurable from a dashboard or API, recordings can land in the customer's own S3 bucket where the vendor stores nothing, and deletion runs via the Recordings page or API. Consent collection is explicitly the customer's responsibility and Whereby-provided storage is not deleted automatically, and we found no public information on automatic retention policies, access logging for recordings, or transcription-specific retention. 3 12 8 4
The Skeptic
Recording is genuinely configurable — auto-start, prompt-host or manual triggers, set from the dashboard or API — with storage either in the customer's own S3 bucket (where Whereby stores nothing) or opt-in paid Whereby storage, deletable through the recordings page or the Recordings API, and 30 GB-days included on the Build plan. Consent to record is the customer's responsibility to collect before starting, Whereby states it would not delete media files automatically, the overage fee above the free quota is acknowledged with its price not stated on the page, and for the Meetings product only local, in-browser recording is available. We found no public information on in-product participant notification, access logs for recordings, retention policies, or attendance and analytics features that a works council could switch off. 3 4 12
Integrations & deployment
Show reasoningHide reasoning
How this is scored
Calendar, identity and the wider stack — plus, in this category, whether the product can be run on the customer's own infrastructure at all.
0 — A closed meeting tool: no calendar integration, no SSO and no API.
3 — A calendar integration or add-in for scheduling meetings, or a few named integrations.
5 — Calendar integration for the major suites (Microsoft 365, Google Workspace), SSO, and a documented API or SDK for creating and managing meetings.
8 — The above plus SCIM provisioning, embedding via SDK, webhooks for meeting events, room-system support, and either a self-hosted option or a documented private-cloud deployment.
10 — Deployment is the customer's choice: a genuine on-premises or private-cloud option with the same features, open protocols or open source, embeddable SDKs, and identity integration that does not require the vendor's directory.
The IT Administrator
The API side is real: REST endpoints for meetings, rooms, recordings and transcriptions, webhooks for lifecycle and recording events, SDK embedding with start/stop commands, and code samples in five languages. What I found no public information on is the enterprise glue — no calendar add-in for Microsoft 365 or Google Workspace, no SSO, no SCIM, no room-system support, no self-hosted deployment — so identity and scheduling remain my problem to solve around the product. 1 3 12 13 14
The Security Officer
The API and SDK story is strong: rooms created and deleted programmatically, recordings managed and downloadable, webhooks for session start and end and for recording finished, theming endpoints, and an embeddable web component with code examples in five languages. We found no public information on calendar integration with Microsoft 365 or Google Workspace, single sign-on, SCIM provisioning, room systems, or running the platform on your own infrastructure — the self-hosted element shown is recordings in your own S3 bucket. 1 3 13 14
The Works Council Advocate
A deeply documented REST API and SDK cover programmatic room creation and deletion, theming, recordings with pagination and sorting, transcriptions and summaries, with webhooks for session start and end and recording completion, alongside named in-meeting integrations including Google Drive, YouTube, Trello and Miro. We found no public information on calendar add-ins for Microsoft 365 or Google Workspace, SSO, SCIM provisioning, or a self-hosted or private-cloud deployment. 1 3 11 12 13
The Educator
The API is deep and genuinely documented: programmatic room creation and deletion, a recordings API with sorting and pagination, webhooks for session lifecycle and recording uploads, theming endpoints for logos, colours and backgrounds, SDK Web Component commands, and code examples in cURL, PHP, Node, Python and Java. In-room integrations are named — Google Drive, YouTube, Trello, Miro. We found no public information on calendar add-ins for Microsoft 365 or Google Workspace, SSO, or SCIM provisioning, and the only self-hosted element shown is customer-managed S3 storage for recordings rather than a deployment of the product itself. 13 14 3 12
The Accessibility Advocate
A documented REST API for meetings, rooms, recordings, transcriptions and summaries, an SDK with start and stop recording commands, webhooks for session lifecycle and recording completion, and code examples in five languages make this a genuine developer platform. The named integrations are in-room tools such as Google Drive and Miro; we found no public information on calendar integration with Microsoft 365 or Google Workspace, SSO, or SCIM provisioning, and self-hosting extends to recording storage rather than the product itself. 13 14 12 3 1
The Skeptic
The REST API is documented in unusual depth — rooms, meetings, recordings, transcriptions, summaries and insights endpoints, bearer authentication, rate limits, pagination and theming — plus webhooks for session start and end and a recording-finished event, and SDK commands to start and stop recordings from an embeddable Web Component. Named integrations exist inside rooms (Google Drive, YouTube, Trello, Miro). We found no public information on calendar integrations with Microsoft 365 or Google Workspace, on SSO, SCIM provisioning, room-system support or a self-hosted deployment of the product itself. 3 12 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where media and metadata are processed, who the contracting entity is, which subprocessors carry the traffic. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and media routed outside the EU, with no EU option stated.
3 — One European element proven — EU data residency for storage, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated for meetings as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (relays, analytics, support tooling, transcription) is unstated or partly non-EU.
8 — Media and metadata processed in the EU on named infrastructure, EU contracting entity, subprocessor list published with locations, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: media never leaves the EU, every subprocessor European, certification published, and an on-premises option that removes the question entirely.
The IT Administrator
Core infrastructure and account data sit on AWS in Dublin, transcription runs on EU-based servers, the contracting entity is Whereby AS in Norway under the Norwegian supervisory authority, and a DPA is offered. But usage information is also hosted in the United States, the network allowlist names US analytics, error-tracking and support tooling, and the subprocessor disclosure stops at categories without names or locations — for a buyer weighing this category heavily, that gap in the chain decides the score. 3 4 7 8
The Security Officer
The contracting entity is Whereby AS in Norway, core infrastructure is named as AWS in Dublin with account data in Ireland, transcription runs through EU-based servers, and United States transfers carry Standard Contractual Clauses. But usage information is also hosted in the United States, TURN relays are described as placed across the globe with no stated region for media, and subprocessors are published only as categories — analysis tools, support tools, marketing — with no names or locations. 3 4 7 8
The Works Council Advocate
Core infrastructure runs on AWS in Dublin with account data in Ireland and all transcription processed through EU-based servers, the contracting entity is Norwegian with the Datatilsynet as supervisory authority, and a Data Processing Agreement is available. But usage information is also hosted in the United States under Standard Contractual Clauses, the TURN relay network is placed across the globe, and subprocessors are published only as categories — including analysis and support tooling — with no names or locations. 3 4 7 8
The Educator
The core is named: Whereby AS of Norway as contracting entity, infrastructure relying mostly on AWS Dublin with account data in Ireland, transcription processed through EU-based servers, media stored not at all, and United States processing of usage information named with Standard Contractual Clauses as the safeguard. Subprocessors, however, are published only as categories — hosting, payment processors including debt collectors, analysis, support, marketing — with no names or locations, and group offices sit in Norway, the United Kingdom and the United States. That is a solid European footing with the chain only half-lit. 3 4 8
The Accessibility Advocate
Core infrastructure sits on AWS Dublin with account data in Ireland, transcription processing through EU-based servers, a DPA offered, a Norwegian contracting entity under the Norwegian Data Protection Authority, and the vendor stating that no media is stored. Usage information is also hosted in the United States under SCCs and the subprocessor disclosure stops at categories — the network allowlist names PostHog, Sentry and HelpScout without locations — so the chain is not evidenced end to end. 3 4 8 7
The Skeptic
The chain is partly documented and partly open: Whereby AS of Norway is the contracting entity with Datatilsynet as supervisory authority, account data sits in Ireland on mostly AWS Dublin, transcription runs through EU-based servers, and a Data Processing Agreement is linked from the docs. Against that, usage information is also hosted in the United States under Standard Contractual Clauses, group companies operate in Norway, the UK and the US, and the published subprocessor list gives categories only, without named vendors or locations — analytics, support and CDN providers surface solely in a network allowlist. We found no public information on hosting options such as a private-cloud or on-premises path. 3 4 8
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the annual invoice for their host count — including the capacity, dial-in and recording storage they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier per host or user.
5 — Per-host or per-user prices public for the main tiers with the billing period stated and participant limits per tier given.
8 — Every tier and add-on priced publicly with per-host maths, capacity limits, dial-in rates, storage allowances, minimum term and VAT treatment stated.
10 — Complete price computability: a calculator producing the annual invoice for a given host count, meeting size and recording volume, including overage and per-region dial-in.
The IT Administrator
The public numbers I can find are per-minute caption add-ons ($0.0065 and $0.024 per unmuted participant minute, $0.0055 pre-purchased on the annual enterprise plan) plus an included storage quota, while a storage overage fee is mentioned with no figure stated. I found no public information on plan prices per user or host, participant limits per tier, billing terms, VAT treatment or dial-in rates, so I cannot compute an annual invoice for any host count. 2 10 12
The Security Officer
Precise public unit prices exist for live captions — $0.0065 per unmuted participant minute on the Build monthly plan, $0.0055 per unmuted participant minute pre-purchased on annual Enterprise — plus a 30 GB-days storage allowance with worked examples. But we found no public per-user or per-host price for either product, and the storage overage fee is acknowledged without a figure, so the annual invoice is not computable from these pages. 2 10 12
The Works Council Advocate
Unit prices are public for live captions across plans ($0.0065 per unmuted participant minute on the monthly Build plan, $0.0055 pre-purchased on annual Enterprise, $0.024 for secondary languages), the billing unit itself is defined, and the included storage is described concretely as 30 GB-days. We found no public information on the price of the per-user Meetings tiers or the usage-based Embedded tiers, and the storage overage fee is mentioned without an amount. 2 10 12
The Educator
Two pricing surfaces exist — Meetings 'Charged per user license' and Embedded 'Charged by usage' — and usage units are priced precisely: live captions at $0.0065 per unmuted participant minute on the Build monthly plan, $0.0055 per unmuted participant minute pre-purchased on the Enterprise annual plan, $0.024 per unmuted participant minute for secondary languages, and 30 GB-days of storage included for Build. But we found no public plan prices per host or per user, no participant limits per tier, and the storage overage fee is acknowledged without its price stated, so an annual invoice is not computable from the captured pages. 10 12 2 1
The Accessibility Advocate
Public pages give usage-unit prices — live captions at $0.0065 per unmuted participant minute on Build monthly, $0.0055 pre-purchased on Enterprise annual, $0.024 for secondary languages, and a 30 GB-day storage quota on Build — plus billing models of per user license for Meetings and by usage for Embedded. We found no per-user or per-host tier price, billing period per tier, or participant limits on the captured pricing pages, and the storage overage fee applies without a price on the page, so an annual invoice is not computable from what we read. 2 10 12 1
The Skeptic
No per-user or per-host plan price appears anywhere we read — the pricing hub links out to separate Meetings and Embedded pricing pages without figures — and the storage overage fee above the free quota is acknowledged with its price not stated on the page. The only exact prices found are usage components: live captions at $0.0065 per unmuted participant minute on the Build monthly plan ($0.0055 per unmuted participant minute pre-purchased on the annual Enterprise plan, $0.024 per unmuted participant minute for secondary languages) against a 30 GB-day storage allowance. We found no public information on dial-in rates, VAT treatment, minimum terms or participant limits per tier, so an annual invoice cannot be computed from these pages. 2 10 12
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in NO
unverified
Why unverified?The privacy policy mentions group companies with facilities in Norway, the UK and the US, but no excerpt names any parent above Whereby AS. |
2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Usage information is also hosted in the United States, so hosting is not EU-only; the security page likewise says infrastructure relies 'mostly' on the AWS Dublin availability zone. |
2/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The docs page lists the Data Processing Agreement as a linked resource, but the excerpt shows neither the agreement's text nor an online conclusion flow. |
1/1 pts | 8 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Whereby
Is Whereby European?
Yes, though not from the EU. whats-best.ai classifies Whereby as UK / wider Europe. Its vendor, Whereby AS, is incorporated in Norway, per the vendor’s page captured 16 Nov 2026.
Where does Whereby store data?
Whereby stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention Ireland as hosting location, per the vendor’s page captured 16 Nov 2026.
Does Whereby have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Whereby?
As of 19 Nov 2026, the panel rates Tixeo (3.5/5), alfaview (3.5/5) and Nextcloud Talk (3/5) highest among the other 33 Video Conferencing products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is alfaview (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Whereby alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 19 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The docs page lists the Data Processing Agreement as a linked resource, but the excerpt shows neither the agreement's text nor an online conclusion flow.
- Weak sourcing — Legal entity. The privacy policy mentions group companies with facilities in Norway, the UK and the US, but no excerpt names any parent above Whereby AS.
- Weak sourcing — Hosting location. Usage information is also hosted in the United States, so hosting is not EU-only; the security page likewise says infrastructure relies 'mostly' on the AWS Dublin availability zone.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 18 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage whereby.com Checked 16 Nov 2026 Details →
- 2 Pricing whereby.com Checked 16 Nov 2026 Details →
- 3 Privacy policy whereby.com Checked 16 Nov 2026 Details →
- 4 Security / trust page whereby.com Checked 16 Nov 2026 Details →
- 5 The meeting itself — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 6 The meeting itself — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 7 Encryption & meeting access — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 8 Encryption & meeting access — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 9 Reach & accessibility — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 10 Reach & accessibility — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 11 Recordings, retention & admin control — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 12 Recordings, retention & admin control — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 13 Integrations & deployment — found from sitemap docs.whereby.com Checked 16 Nov 2026 Details →
- 14 Integrations & deployment — found from sitemap docs.whereby.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 15 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →