Nextcloud Talk vs Jitsi: Which One Actually Fits Your Team?

Both are open source, and both let you keep calls on infrastructure you control. So the real question isn't which one has a longer checklist. It's which one matches the way your team already works.

Nextcloud Talk is part of a broader collaboration suite: chat, files, calendars, and calls all tied to one login. Jitsi Meet is a video meeting server, full stop, designed so someone can click a link and join a call. Almost every difference between them comes back to that.

This guide compares them on the things that decide a real rollout: call size, setup effort, guest access, recording, and cost. If you are weighing Jitsi against other video options too, see our BigBlueButton vs Jitsi comparison and LiveKit vs Jitsi.

Four Questions That Settle It

Forget the giant comparison spreadsheet for a minute. These four questions usually decide it:

1. Are you already running Nextcloud? If yes, Talk is probably already there and uses your existing accounts. If no, adopting Talk means adopting Nextcloud too, a much bigger project than just adding video.
2. Who is joining the calls? Staff with accounts? Or clients, candidates, and outside guests who should click a link and be in the meeting seconds later?
3. How large do your calls get? A six-person stand-up is a very different problem from a 100-person all-hands.
4. Do you need chat that survives after the call ends? Talk keeps conversation history. Jitsi's chat is mostly tied to the meeting itself.

Nextcloud Talk: Calls Inside Your Collaboration Suite

Nextcloud Talk is the chat and video app that comes with Nextcloud, released under the AGPLv3+ license. Its biggest advantage is context. A conversation can live beside the files, calendar events, and tasks it's about, and your users don't need yet another login.

The catch is how it handles connections, which the next section covers. First, what you get:

• One-to-one and group calls, plus persistent chat with file sharing from Nextcloud storage
• Guest access through a public link, with a lobby so moderators control who gets in
• Breakout rooms and call recording (both arrived in Talk 16, released March 2023, and require the High-performance backend)
• SIP dial-in for phone participants, available through the High-performance backend setup
• Native Android and iOS apps, plus desktop clients for Windows, macOS, and Linux
• Federation between Nextcloud servers, allowing cross-instance chat

The Math Behind Talk's Call Size

By default, Talk calls are peer to peer: each person sends video directly to everyone else. That's fine for two or three people, but it gets heavy quickly. Talk's own scalability docs explain the math.

The docs say a 20-person call with no video could be doable on fast connections, but the load on browsers and mobile devices remains a real constraint. For bigger calls, you add the High-performance Backend (HPB): a signaling server (nextcloud-spreed-signaling) and a WebRTC media gateway that turns the call into an SFU setup. The same docs say that scales to 30 to 50 or more active participants, and to hundreds of passive ones, which suits webinars or remote teaching.

Jitsi Meet: A Video Server Built for Joining by Link

Jitsi Meet is Apache 2.0 licensed and built around the Jitsi Videobridge, an SFU, from day one. You don't need to install or configure a separate media server just to get past a few participants: deploy Jitsi and group calls work. Anyone with the link can join from a browser, no account required. That's why it's usually the go-to for meetings with people outside your company.

In Meetrix's own capacity testing, a single Jitsi conference held up comfortably to around 200 to 250 participants before the frontend, not the server, started to struggle. Beyond that, the frontend showed signs of strain: at 500 participants there were minor UI delays, and by 1,250 the interface became noticeably laggy. The backend itself remained stable throughout; the bottleneck was the browser rendering the meeting. We cover the limits in more detail in our 1000-user capacity write-up.

• Join from a browser link, with no account or install
• Native breakout rooms, lobby, screen sharing, and raise hand
• Recording and live streaming through Jibri, which runs as a separate component and captures the conference via a virtual framebuffer
• SSO through JWT authentication, with Keycloak and other OIDC providers supported via adapter libraries
• Optional end-to-end encryption using insertable streams, supported in Chrome, Edge, and Safari (but not for chat, and not compatible with recording). See our Jitsi encryption guide
• Iframe and JavaScript API for embedding Jitsi into your own product

Setup and Running Costs

Jitsi is one product to deploy for video: the web app, Jicofo, Prosody, and the videobridge. Add Jibri if you want recordings, and note that Jibri runs best on a separate machine, since it needs exclusive access to display and audio devices. Add a TURN server if you expect people behind strict firewalls. Our self-hosting cost breakdown shows what that bill looks like in practice.

Talk looks cheaper on day one. If Nextcloud is already running, two-person calls just work. The cost arrives with the first big call. Past about four people, you'll want the High-performance backend, and that's its own set of services to install, secure, and monitor, alongside TURN. Nextcloud's own quick-install docs note that even three-participant calls benefit from the HPB, cutting required upload bandwidth by 50%. A realistic starting point for a production HPB deployment without recording is a modern 8-core CPU with around 16 GB of RAM, according to community production reports.

If you're standing up Nextcloud anyway, that's a reasonable add-on. If you're only after video, you're building a lot of infrastructure around one feature, and I wouldn't.

Neither product has a license fee in its open-source form. Your real cost is the server, bandwidth, and the hours of whoever runs it.

Nextcloud Talk vs Jitsi: Feature Comparison

Check each project's current release notes before you commit. Both move quickly, and features such as recording and breakout rooms are recent additions on the Talk side.

Can You Use Both?

Yes, and for a team that has both needs, that's the split I'd pick. Talk handles daily conversation and small calls among staff, while Jitsi handles webinars, client calls, and anything large. There's a Jitsi integration app for Nextcloud that starts a Jitsi meeting from inside it, so people don't have to leave the workspace. You still run the Jitsi server separately.

If Nextcloud is already your file layer, our Nextcloud developer guide shows how to deploy it, and the Nextcloud store page has the AWS listing.

Where Meetrix Fits

We package Jitsi Meet as pre-configured images for AWS and Google Cloud, in plans from 50 to 500 users, with or without recording. TURN configuration, SSL, and videobridge setup are done before you launch, which is usually the part that takes the longest when you build it by hand. See the Jitsi Meet store page for plans, or the AWS developer guide for the full launch walkthrough.

We don't sell Nextcloud Talk as a separate product. If Talk is the right answer for your team, that's the right answer, and the Nextcloud documentation is the place to start.

Common Mistakes

• Running Talk without the High-performance backend for bigger calls. Peer to peer is fine for a few people. Past that, upload bandwidth and device load become the limit.
• Adopting Nextcloud just for video. You end up running a whole collaboration suite, plus the backend, around one feature.
• Expecting Jitsi to replace team chat. Its chat lives and dies with the meeting. It's a meeting room, not a workspace.
• Forgetting TURN. People behind strict firewalls can't connect in either product without it.
• Counting on recording and end-to-end encryption together. Jibri can't record a Jitsi meeting that uses end-to-end encryption.

Where I'd Start