Competitor Analysis · Zoom

Everyone joined Zoom during COVID.
US authorities never left.

Zoom Video Communications is a US company headquartered in San Jose, California. Under the CLOUD Act (18 U.S.C. § 2713), every meeting recording, AI Companion transcript, and message handled through Zoom infrastructure is subject to US government compelled disclosure — regardless of where your data centre is located. Sweden's government has formally advised against Zoom. The EU Commission is now preparing legislation to restrict US cloud providers from processing sensitive public sector data.

Switch to sovereign → See the comparison
Zoom: Zoom Inc. (US) jurisdiction Zoom AI Companion processes all meeting content AMVLET: No US jurisdiction. No exceptions.
2026 alerts
Sweden's eSam formally advises all 34 central government bodies against Zoom
EU Commission "Tech Sovereignty Package" — May 2026 — proposes US cloud restrictions for sensitive public data
CLOUD Act: jurisdiction follows provider nationality, not data location — Zoom is always US jurisdiction
Saudi PDPL Art. 29: Zoom CLOUD Act compliance structurally conflicts with KSA data sovereignty requirements
$220/yr
Zoom Business per user per year — every meeting, recording, and AI Companion transcript on that plan flows through Zoom's US-jurisdiction cloud infrastructure, fully accessible under the CLOUD Act
0
GDPR Article 48 mechanisms that permit lawful CLOUD Act compliance for Zoom users — the structural conflict between EU data protection law and US compelled disclosure is unresolved for all Zoom products
100%
Of Zoom paid plans store cloud recordings and process AI meeting summaries on Zoom-controlled US infrastructure — Zoom's Law Enforcement Response System (LERS) is a dedicated compliance channel for government data requests
1:1
The Matrix open standard maps directly to every Zoom feature — video, voice, messaging, recording, AI — with full data sovereignty, no US jurisdiction, and zero per-seat licensing on self-hosted deployments
Feature comparison

Zoom vs AMVLET — every feature, every exposure

The same meetings, recordings, and AI capabilities — with one critical difference: who has legal access to the data.

Feature Zoom Basic $0 Zoom Pro Zoom Business Zoom Enterprise AMVLET · Matrix Sovereign
Meetings & Video
Video conferencing
Meeting duration limit 40 min 30 hours 30 hours 30 hours No limit
Max attendees 100 100 300 500+ Unlimited
Screen sharing
Breakout rooms
Webinars Add-on Add-on
Recording & Storage
Local recording
Cloud recording Zoom cloud — 5 GB Zoom cloud — unlimited Zoom cloud — unlimited Your sovereign storage
Recording jurisdiction Zoom / US Zoom / US Zoom / US Your jurisdiction
AI & Transcription
AI meeting summaries Zoom AI Companion Zoom AI Companion Zoom AI Companion Optional — on-prem
AI transcription Zoom processes content Zoom processes content Zoom processes content Optional — sovereign
AI smart chapters & next steps Zoom AI — US jurisdiction Zoom AI — US jurisdiction Zoom AI — US jurisdiction Optional — sovereign
AI data jurisdiction Zoom / US Zoom / US Zoom / US Your jurisdiction
Messaging & Calling
Persistent messaging (Zoom Chat)
Voice & video calling
Phone (PSTN calling) Add-on Add-on
End-to-end encryption Optional — limited Optional — limited Optional — limited Optional — limited E2EE by default
Sovereignty & Security
Data jurisdiction Zoom / USA Zoom / USA Zoom / USA Zoom / USA Your jurisdiction
CLOUD Act exposure YES — Zoom YES — Zoom YES — Zoom YES — Zoom NO
GDPR Art. 48 conflict YES YES YES YES None
PDPL (Saudi Arabia) conflict YES YES YES YES None
Gag order risk (§ 2705(b)) YES YES YES YES Not applicable
Government data request system LERS — built-in LERS — built-in LERS — built-in LERS — built-in Not applicable
Self-hostable
Air-gapped deployment
Cryptographic key ownership Zoom Zoom Zoom Zoom (partial BYOK) You
Open Standard & Federation
Open standard protocol Proprietary Proprietary Proprietary Proprietary Matrix (open)
Interoperable federation ✓ Cross-org
Vendor lock-in Zoom Zoom Zoom Zoom None
Interchangeable clients
NIS2 supply-chain compliance Cannot satisfy Cannot satisfy Cannot satisfy Cannot satisfy Full documentation
EU Tech Sovereignty Package ready No No No No Yes
The Zoom exposure

What Zoom exposes under the CLOUD Act

Zoom Video Communications Inc. is headquartered in San Jose, California. Every service it provides — regardless of data centre location — falls under US jurisdiction. Zoom even operates a dedicated government compliance system: its Law Enforcement Response System (LERS).

Critical

Cloud recordings and Zoom AI Companion transcripts

Every cloud recording stored on Zoom, and every AI Companion-generated transcript, meeting summary, smart chapter, and action item, is held on Zoom-controlled US infrastructure. A single CLOUD Act order compels Zoom to produce complete recordings and AI-derived intelligence from your most sensitive meetings — board sessions, M&A discussions, legal strategy, personnel matters — without notifying you. Zoom's own Transparency Report documents thousands of such government data requests annually.

CLOUD Act § 2713 · Compelled disclosure of stored communications regardless of location
Structural

Zoom's LERS makes compliance faster, not safer for you

Zoom operates a dedicated Law Enforcement Response System (LERS) — a streamlined channel specifically designed to process government data requests efficiently. While Zoom presents this as a transparency measure, LERS means US law enforcement has a purpose-built, low-friction path to your meeting data. Zoom's "Node Survivability Modules" address connectivity resilience during network outages — they are not a CLOUD Act solution. They do not change jurisdiction and provide no legal protection against compelled disclosure.

CLOUD Act § 2713 + 18 U.S.C. § 2703 · LERS — dedicated compliance channel for government data requests
High Risk

Zoom Chat messages and file transfers

Zoom Chat — the persistent messaging component of Zoom Workplace — stores all message history, file attachments, and shared content on Zoom's US-controlled servers. Enterprise messaging contains highly sensitive operational intelligence: decision trails, document drafts, confidential attachments, and strategic discussions. Sweden's eSam, representing 34 central government agencies, concluded that this data exposure to US jurisdiction made Zoom incompatible with government use. GDPR Article 48 provides no lawful basis to resist a CLOUD Act compelled disclosure.

GDPR Art. 48 + eSam Risk Assessment (2023) · "Sensitive information is at risk"
Structural

PDPL conflict: Saudi Arabia's data is not protected

Saudi Arabia's Personal Data Protection Law (PDPL, Royal Decree M/19) restricts cross-border transfer of personal data outside the Kingdom without NDMO authorisation. When a US CLOUD Act order compels Zoom to produce data of Saudi users or Saudi organisations, Zoom must comply — regardless of PDPL. There is no US–Saudi bilateral executive agreement, no PDPL-compliant transfer mechanism, and no notification right. The conflict is structurally identical to GDPR Article 48: following US law means violating Saudi law, and vice versa. No Zoom contractual assurance resolves this.

PDPL Art. 29 (KSA) + CLOUD Act § 2713 · Cross-border transfer without NDMO authorisation
Silent Risk

Gag orders: you will never be notified

Under 18 U.S.C. § 2705(b), US authorities can attach a non-disclosure order to a CLOUD Act demand, legally prohibiting Zoom from informing you that your data was requested or produced. This directly violates GDPR's transparency obligations (Articles 13–14) and eliminates any practical ability to challenge the disclosure. Your government ministry, legal team, or board may have had their most sensitive discussions reviewed by a foreign government — and the law ensures you never find out. Zoom's own Transparency Report confirms it regularly receives and complies with such requests.

18 U.S.C. § 2705(b) + GDPR Arts. 13–14 · Compelled non-disclosure violates EU transparency obligations
Legislative

EU Commission is moving to restrict Zoom and US cloud for sensitive data

In May 2026, the European Commission confirmed it is preparing its "Tech Sovereignty Package" — including the Cloud and AI Development Act (CADA) — which will propose restricting US cloud providers from processing sensitive public sector data, including financial, judicial, and health data. Under these proposals, EU government bodies may be required to use European sovereign cloud infrastructure for their most sensitive workloads. Zoom, as a US-headquartered provider, would fall directly within the scope of these restrictions. The direction of European regulation is unambiguous: US providers are being structurally excluded from sensitive public sector use.

EU CADA (proposed May 2026) + CLOUD Act § 2713 · US providers to face restrictions in sensitive EU public sector data
The open standard advantage

Matrix: the sovereign backbone that replaces Zoom — without the exposure

The Matrix open standard (spec.matrix.org) delivers everything Zoom offers — meetings, messaging, voice, video, file sharing, AI, webinars — on an open, vendor-neutral protocol where your organisation controls its own server, its own data, and its own encryption keys. No Zoom, no US jurisdiction, no LERS, no CLOUD Act applicability at any layer.

Zoom was the world's meeting room during COVID. But convenience was never the same as sovereignty. Zoom's architecture requires your communications to flow through US-controlled infrastructure for every call, every recording, every AI summary — making CLOUD Act exposure a structural fact, not a manageable risk. Matrix eliminates that architecture entirely.

AMVLET is built on Element Server Suite (ESS Pro), the enterprise-grade implementation of the Matrix standard. For EU organisations subject to GDPR and the incoming CADA legislation, and for organisations in Saudi Arabia subject to PDPL, Matrix is the only architecturally sound path: a communications platform where CLOUD Act compelled disclosure is not a risk to manage — it is a structural impossibility.

Read the Matrix specification →
No US jurisdiction at any layer — CLOUD Act inapplicable
Matrix servers deploy in your own data centre, a sovereign EU cloud, or a KSA-resident facility. No Zoom, no US infrastructure at any point in the architecture. CLOUD Act compelled disclosure is not mitigated — it is structurally impossible because no US company controls the data.
End-to-end encryption by default — no Zoom key access
Matrix encrypts messages end-to-end with keys generated on your devices. Zoom's E2EE is optional, limited in scope, and excludes cloud recording and AI features. With Matrix, nobody — including AMVLET — can decrypt your communications. A CLOUD Act order directed at AMVLET would produce nothing decryptable.
GDPR and PDPL compliance by architecture
When no US company is in the data path, the GDPR Article 48 conflict and the Saudi PDPL Article 29 conflict cease to exist. Compliance is an architectural fact — not a contractual assurance from a US company that remains subject to US law regardless of what its contracts say.
Open standard federation between organisations
Zoom routes all external communications through its own infrastructure. Matrix enables direct server-to-server federation — each organisation runs its own server, and servers communicate directly. No US intermediary handles inter-organisational meetings, messages, or calls.
EU Tech Sovereignty Package ready — today
As the EU Commission moves to restrict US cloud providers from sensitive public sector data, AMVLET on Matrix is the ready answer. No legislative risk, no procurement risk, no compliance rework required. The architecture that will satisfy the incoming CADA regulation is available now.
The platform choice

What you accept when you choose Zoom vs. what you control with Matrix

Zoom — what you accept

Zoom holds your meetings. US law reaches every one of them.

  • All cloud recordings and AI Companion transcripts stored on Zoom's US-jurisdiction infrastructure — fully compellable under the CLOUD Act
  • Zoom's LERS system provides a purpose-built, low-friction channel for US government data requests against your communications
  • Gag orders under § 2705(b) mean you will not be notified when your meeting data is produced to US authorities
  • GDPR Article 48 conflict is structural and unresolvable — Sweden's government formally advises against Zoom for this reason
  • Saudi PDPL Article 29 conflict is equally unresolvable — no US–KSA executive agreement exists, no NDMO-compliant path for CLOUD Act compliance
  • EU Commission's CADA legislation (2026) is moving to restrict Zoom and US providers from sensitive public sector data
  • Vendor lock-in: switching means losing all message history, recordings, and rebuilding all integrations on Zoom's proprietary protocol
VS
AMVLET · Matrix — what you control

Your infrastructure. Your keys. Your jurisdiction.

  • No US company in the data path — CLOUD Act applicability is structurally eliminated, not contractually managed
  • No LERS, no Law Enforcement Response System, no dedicated government compliance channel in the data path
  • GDPR and PDPL compliance by architecture: data stays in the jurisdiction where it is governed
  • Cryptographic keys generated and held on your infrastructure — AMVLET cannot decrypt your content
  • AI processing optional, deployable on your own sovereign infrastructure within your jurisdiction
  • EU CADA-ready today — sovereign architecture satisfies the incoming EU Tech Sovereignty Package requirements
  • No vendor lock-in: Matrix is an open standard — your data, your deployment, your jurisdiction, permanently
Common questions

Switching from Zoom: what organisations ask

Zoom says it stores European data in European data centres. Doesn't that resolve the CLOUD Act problem?+
No. This is the single most common misunderstanding about cloud sovereignty. The CLOUD Act (18 U.S.C. § 2713) applies based on the nationality of the provider — not the physical location of the data. Zoom Video Communications Inc. is incorporated in the United States and headquartered in San Jose, California. A CLOUD Act order compels Zoom to produce data from any server it operates, anywhere in the world, including those located in Frankfurt, Amsterdam, or Dublin. Choosing a "European data centre" in Zoom's settings has no legal effect on this obligation. Sweden's eSam, which conducted a comprehensive risk assessment of Zoom on behalf of 34 central government agencies, reached the same conclusion: the structural CLOUD Act exposure remains regardless of data centre location. Their formal recommendation: do not use Zoom for government communications involving sensitive information.
Does Zoom's Law Enforcement Response System (LERS) protect me, or does it make my risk worse?+
LERS makes the risk more structured — for Zoom and for US authorities — but it does not protect you. The Law Enforcement Response System is Zoom's dedicated operational channel for processing government data requests. It is designed to make Zoom's compliance with legal orders faster and more efficient. For users and organisations, this means that when a CLOUD Act order arrives for your data, Zoom has an optimised process for fulfilling it. Zoom's Transparency Reports confirm it regularly receives and complies with government data requests through this mechanism. LERS is a compliance infrastructure, not a protection mechanism. Its existence is evidence of the structural CLOUD Act exposure — not a mitigation of it.
Does Zoom's CLOUD Act exposure create a conflict with Saudi Arabia's PDPL?+
Yes — and the conflict is structurally unresolvable. Saudi Arabia's Personal Data Protection Law (PDPL, Royal Decree M/19) restricts the cross-border transfer of personal data outside the Kingdom without prior authorisation from the National Data Management Office (NDMO). When a US CLOUD Act order compels Zoom to produce data belonging to Saudi organisations or Saudi users, Zoom must comply under US law. There is no US–Saudi Arabia bilateral CLOUD Act executive agreement (the US has such agreements only with the UK and Australia as of 2025). There is no PDPL-compliant mechanism to legitimise a CLOUD Act compelled disclosure. The organisation subject to the order would simultaneously violate PDPL and be unable to prevent it. For Saudi government entities, financial institutions, healthcare organisations, and enterprises handling sensitive citizen data, this makes Zoom structurally non-compliant with national data sovereignty requirements.
What is the EU's Tech Sovereignty Package and how does it affect Zoom?+
In May 2026, the European Commission confirmed it is preparing a "Tech Sovereignty Package," expected to be presented to EU member states that month. The package includes the Cloud and AI Development Act (CADA), which proposes restricting the use of non-EU cloud providers — including US providers like Zoom — for processing sensitive public sector data, including financial, judicial, and health data. If adopted by all 27 member states, EU government bodies and public-sector organisations could be legally required to use sovereign cloud infrastructure for their most sensitive workloads. Zoom, as a US-headquartered provider with full CLOUD Act exposure, would fall directly within the scope of these restrictions. The practical implication for organisations currently using Zoom for government or public sector work: the procurement and compliance risk is escalating rapidly. The architecture that will satisfy CADA is available today through AMVLET and the Matrix open standard.
Can Matrix/Element really match all the features of Zoom?+
Yes. The Matrix standard covers the full communication stack: persistent encrypted messaging (equivalent to Zoom Chat), voice and video calling, group meetings with screen sharing and breakout rooms, webinar-scale broadcasts, file sharing, and — with AMVLET's deployment — meeting recording stored on your own sovereign infrastructure. For AI features (transcription, meeting summaries, smart chapters, action items — equivalent to Zoom AI Companion), AMVLET supports optional on-premise AI processing, meaning the AI runs on your infrastructure with no data leaving your jurisdiction. The critical architectural difference is that Matrix separates the client from the server: your organisation chooses its own frontend, runs it against its own server, and federates with partner organisations — all without any US company in the data path. What Zoom cannot offer is sovereignty. What Matrix cannot offer is the ability to secretly disclose your data to a foreign government — because architecturally, no single party holds the keys to your communications.

The same meetings. None of Zoom's exposure.

Switch from Zoom to a sovereign communications platform that gives you every feature — without putting your most sensitive conversations under US jurisdiction or in scope for the EU's incoming Tech Sovereignty regulation.

Book a migration briefing → Explore Enterprise