Jitsi Meet vs Nextcloud Talk

Jitsi Meet

Screen sharing, integrated chat and HD Opus audio are stated, and the selective-forwarding architecture comes with published load numbers — 1056 streams at over 550 Mbps for about 20% CPU — plus a Last-N mode that trims distribution to the most recent speakers and distributed tracing across the backend. What I could not find is a published participant cap per meeting, breakout rooms, or a lobby; on meet.jit.si moderation is described as "soft, and for everyone" because all users are moderators, with strong authentication available only on instances customers run themselves.

Nextcloud Talk

The only capacity numbers on file are '6-10 participants, up to 20 if all participants have a good network connection and do not use video' for a private setup, and a vague 'thousands' for enterprise — nothing tied to a plan. Breakout rooms exist and the constrained-connection honesty is welcome, but the webinar lobby needs the High Performance Backend, and screen sharing, mute-all, waiting rooms and any bandwidth-adaptation claim are simply absent from the evidence.

Jitsi Meet

The sentence I look for exists: end-to-end encryption can be switched on per meeting via a shared password entered by all participants, the extra layer "is never removed (nor can it be)" at the server, and the pages name the trade-offs plainly — it "doesn't cover chat, polls, etc." and needs Chromium 83 or the Electron client. The cryptography is open source under Apache 2.0 and the pages state what is tracked and when it is destroyed. But meeting access rests on an optional meeting password and an unpredictable room name; we found no public information on a lobby, single sign-on gated joining, or any verification of who a participant is.

Nextcloud Talk

'Multi-layered encryption' appears once, in a bug-bounty marketing sentence — no page says which meetings are end-to-end encrypted, with what key handling, or which features stop working when it's on. The one substantive statement is that Nextcloud hosts nothing and its employees never gain access to customer data, which inverts the vendor-holds-keys problem but is a deployment fact, not a documented crypto mechanism. Access control tops out at a webinar lobby that requires the HPB; no passcodes, no SSO-gated joining anywhere.

Jitsi Meet

Browser meetings without an install, guests joining with no account, and mobile apps on three stores including F-Droid are all stated on the captured pages. Beyond that it thins out fast: we found no public information on listed dial-in numbers (only a URL pattern where a dial-in information page would sit), no accessibility statement or conformance report, and no documented behaviour on poor connections beyond the stream-limiting mode aimed at server load.

Nextcloud Talk

Dial-in exists only through the SIP bridge with the High Performance Backend, and no phone numbers or regions are listed; live transcription with translation is genuinely evidenced and AI is stated optional. Browser joining is implied by 'web' in the platform blurb but never confirmed as full-feature, guest access by link is unmentioned, and there is no accessibility statement of any kind. Mobile apps are the solid part.

Jitsi Meet

The data lifecycle is concrete and public — rooms are destroyed when the last participant leaves, chat and speaker stats go with them, and cloud recordings sit on the servers at most 24 hours before deletion after upload to the customer's Dropbox. Recording happens through the jibri tooling and transcription exists, but for the questions a works council actually asks — who may record, whether participants are notified or asked to consent, which region the servers sit in, and any organisation-wide policy or access log — we found no public information.

Nextcloud Talk

'Recording consent in meetings' is the entire governance record — no admin policy over who may record, no retention rule for recordings or transcripts, no access logging, no audit trail. Storage region is answered only implicitly because the customer self-hosts; the evidence never says so for recordings specifically. Call transcripts, AI summaries and participant-list CSV export are all present, and only the AI is documented as switchable.

Jitsi Meet

Deployment choice is the strong suit: the whole product is Apache-2.0 open source, self-hostable via Docker in about 15 minutes, controllable over XMPP and a REST interface, embeddable through the external API, and offered as a managed service (JaaS) with tenant domains. What the captured pages do not show is the office plumbing — we found no public information on calendar integration, SAML or OIDC single sign-on, SCIM provisioning, webhooks, or room-system support.

Nextcloud Talk

On-premises isn't an option here, it's the product — hostable on-premises, 100% open source, and airgap-capable, which answers the deployment half of this criterion about as well as it can be answered. But the identity and API half is unevidenced: no SSO, no SCIM, no documented scheduling API; what's actually on file is webhook bots, a Pexip bridge, a SIP bridge and an Outlook file-sharing add-in.

Jitsi Meet

The contracting party is 8x8, Inc. of Campbell, California, with all claims litigated exclusively in New York City courts, no statement of where media or metadata are processed, and the analytics services named for meet.jit.si — Amplitude, Datadog, Crashlytics — are US providers. We found no public information on EU hosting, an EU contracting entity, or any published certification. The open-source self-hosted deployment is the one route that takes this vendor out of the chain entirely, but as offered here nothing European is evidenced, and I weigh that heavily.

Nextcloud Talk

Whatever the pipeline's 'unknown' fields say, the imprint is unambiguous: Nextcloud GmbH, Stuttgart, HRB 227086, German VAT ID, external DPO in Munich. Media and metadata live on infrastructure the customer chooses, down to airgap, which removes the question for the bulk of the chain. The deductions are concrete: Nextcloud itself hosts a STUN server, the hosted HPB offering runs 'by our partners' who are never named, and no certification is published.

Jitsi Meet

The headline is honest and extreme — the service is free "all day, every day" with no account, and the open-source download is free as well. But a buyer cannot compute a bill for the commercial path: we found no public information on pricing for the managed JaaS offering, no participant caps are published, and the terms let 8x8, in its sole discretion, require a "transition to a paid service" for exceeding a usage limit the pages never state.

Nextcloud Talk

Per-user prices are admirably public down to VAT treatment — 71.29/104.99/204.75 EUR per user per year, net, from 100 users. But capacity is not tied to any plan tier, and the High Performance Backend — required for both webinars and phone dial-in — carries no price at all, just a 30-day hosted trial. Dial-in rates, recording storage allowances and minimum terms are absent, so I cannot compute the annual invoice for a real deployment from these pages.