whats-best.ai
Search Sign in

Video Conferencing

Zoom

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Zoom Communications, Inc. · zoom.us

Compare with Microsoft Teams → Compare with Google Meet → Report an error on this page Is this your product? →

Read this page as one judge. Each weighs the same scores by what they care about.

The IT Administrator

Weighted verdict

Gets the call when the board meeting will not start. Wants capacity published rather than promised, room systems that work, SSO, and diagnostics after a bad call. Judges a product by its worst meeting, not its demo.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The IT Administrator

The meeting itself

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 — Small meetings only, no screen sharing worth the name, no moderation controls, and the call degrades without telling anyone.

3 — Standard meetings with screen sharing and mute-all, but low participant limits, no breakout rooms and no bandwidth adaptation stated.

5 — Meetings at the scale most teams need with screen sharing, breakout rooms, host moderation, and documented behaviour on constrained connections.

8 — Large meetings and webinars with published capacity limits, per-participant moderation and waiting rooms, layout control, simulcast or adaptive bitrate stated, and reliable behaviour on mobile networks.

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.

Report an error

The IT Administrator

Capacity is published per plan — 100, 100 and 300 participants, webinars at 500, and an add-on path to 5,000 — and breakout rooms are documented down to roles, preassignment and help requests, which is what I want to see rather than promises. Waiting rooms and a mandatory minimum security option are enforced even at the API level, and live streaming is stated. What I found no public information on is adaptive quality under load, hardware room-system support, or diagnostics an admin can read after a bad call. 2 6 7 10 3

Report an error

Encryption & meeting access

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 — Transport encryption only, undocumented; meetings joinable by anyone with a link and no lobby.

3 — TLS in transit and encryption at rest, with the vendor holding all keys; access control is a passcode.

5 — The above plus a lobby or waiting room, host-controlled admission, per-meeting passcodes, and a clear statement that the vendor can technically access media.

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.

Report an error

The IT Administrator

The documented mechanism is TLS 1.2 with 256-bit AES-GCM, per-meeting passcodes, waiting rooms and authenticated-only join, and the API overwrites requests that try to strip every security option — a forced minimum is good engineering. But the captured browser matrix marks end-to-end encryption as not supported across all browsers, and I found no public information on an end-to-end option for meetings, key handling, or a plain statement of what Zoom can see of meeting media; the privacy pages do show account owners and Zoom accessing chat and email content. 9 10 7 3

Report an error

Reach & accessibility

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 — A desktop client is the only way in; guests must create an account.

3 — Browser joining exists but is degraded, guests can join by link, and there is no dial-in and no accessibility statement.

5 — Full-feature browser joining without an install, guest access by link, mobile apps, and a stated accessibility posture.

8 — Telephone dial-in with numbers listed, live captions, keyboard-navigable and screen-reader-tested interface, 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.

Report an error

The IT Administrator

Browser joining is the strongest thing here: the web client feature set is the baseline, live transcription and translation are listed across all captured browsers, and 720p send on mobile browsers is specified by OS version down to iOS 16.4 and Android Chrome 112. However, component view is not supported on mobile or tablet browsers at all, and I found no public information on telephone dial-in, keyboard or screen-reader testing, or documented behaviour on poor connections. 9 10

Report an error

Recordings, retention & admin control

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.

0 — Anyone can record, storage location unstated, no retention rule, no admin policy.

3 — Host-only recording with a notification, but storage region unstated, retention manual, and no organisation-wide policy control.

5 — Admin policy over who may record, participant notification and consent prompt, stated storage region, and manual deletion that works.

8 — Automatic retention and deletion per policy, recordings encrypted at rest with access logged, transcription handled with its own 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 no participant-level behavioural scoring at all.

Report an error

The IT Administrator

There is a recording notification in the terms, a delete-after-a-specified-number-of-days setting, host start/pause/stop control, and a bring-your-own-storage option that puts the files in the customer's own S3 bucket — that last one a works council can live with. I found no public information on the storage region for Zoom-held recordings, a consent prompt, an audit trail of recording access, or independent switches for transcription and analytics. 4 11 12

Report an error

Integrations & deployment

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 — No calendar integration, no SSO, no API; cloud-only with no alternative.

3 — One calendar integration and basic SSO, no API worth building on, cloud-only.

5 — Calendar integration for the major suites, SAML or OIDC SSO, a documented API for scheduling, and room-system support.

8 — The above plus SCIM provisioning, embedding via SDK, webhooks for meeting events, 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.

Report an error

The IT Administrator

The developer surface is broad: calendar APIs with ACL management, meeting create and update APIs, embeddable web SDKs, recording and transcript webhooks, OpenAPI downloads, client libraries, plus SSO and managed domains from the Business tier. I found no public information on SCIM provisioning, hardware room-system support, or any self-hosted or private-cloud deployment — everything captured runs in Zoom's cloud. 2 13 14 9

Report an error

European sovereignty

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.

0 — Non-EU vendor and contracting entity, media routed through unstated regions, subprocessors unnamed.

3 — EU data residency for storage while media relays or metadata remain non-EU, or the contracting entity sits outside the EU.

5 — EU hosting and an EU contracting entity, but parts of the chain — relays, analytics, support tooling, transcription — are non-EU without an explained safeguard.

8 — Media and metadata processed in the EU on named infrastructure, EU contracting entity, complete subprocessor list published, 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.

Report an error

The IT Administrator

The contracting entity is Zoom Communications, Inc. of San Jose with the Data Protection Officer at the same address, enforcement sits with the Federal Trade Commission, and transfers to Europe rely on standard contractual clauses and the Data Privacy Framework — a US arrangement end to end. The captured pages leave media and metadata residency unstated and name no subprocessors beyond a generic mention of third-party providers, so we found no public information a European buyer could verify against. 4 3

Report an error

Pricing transparency

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 per-host headline exists, but participant caps, dial-in minutes or recording storage are unpriced or unmentioned.

5 — Per-host prices public with billing period stated and capacity limits given, but at least one commonly needed piece (webinar capacity, dial-in, storage) sits in an unpriced add-on.

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.

Report an error

The IT Administrator

Per-host prices are public with billing period and VAT treatment stated — €13.33 and €17.49 per user per month billed annually excluding VAT, a free tier with its 40-minute and 100-participant limits, 10 GB cloud storage per licence, and a large-meeting add-on from €46.50 for 500 participants. But that add-on is priced only from a floor, I found no public information on dial-in rates or the subscription term length, and the captured pages give different signals on AI cost — a no-extra-cost claim on the homepage beside per-feature charges in the developer documentation. 1 2 4 11

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Where this could be wrong

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.

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage zoom.us Checked 15 Sep 2026 Details →
  2. 2 Pricing zoom.us Checked 15 Sep 2026 Details →
  3. 3 Privacy policy explore.zoom.us Checked 15 Sep 2026 Details →
  4. 4 Terms of service www.zoom.com Checked 30 Sep 2026 Details →
  5. 5 The meeting itself — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  6. 6 The meeting itself — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  7. 7 Encryption & meeting access — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  8. 8 Encryption & meeting access — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  9. 9 Reach & accessibility — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  10. 10 Reach & accessibility — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  11. 11 Recordings, retention & admin control — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  12. 12 Recordings, retention & admin control — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  13. 13 Integrations & deployment — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →
  14. 14 Integrations & deployment — found from sitemap developers.zoom.us Checked 1 Oct 2026 Details →