Jitsi Meet is the first thing many people think of when it comes to privacy-friendly video conferencing - and for good reason: Jitsi runs in the browser, is open source and can be self-hosted. Briefing runs in the browser and can be self-hosted too, but makes a different architectural choice. This page explains that choice and when each tool is the better fit.
In short
| Briefing | Jitsi Meet | |
|---|---|---|
| Runs in the browser | yes | yes |
| Self-hostable | yes, one Docker image | yes, several services (web, Prosody, Jicofo, videobridge) |
| Account to start a call | no | required for the moderator on meet.jit.si (Google or GitHub account) |
| Path of video and audio | directly between browsers | through the Jitsi Videobridge |
| End-to-end encryption | always | optional, the moderator turns it on per meeting |
| Does the server know the room name? | no, only an irreversible id | yes |
| Admission | participants check cryptographically | server, optional lobby and password |
| Call during a server outage | keeps going | drops |
| Safety codes against eavesdroppers | yes | no |
| Large groups | no, made for small groups | yes |
| Time limit on the free public server | none | 95 min on meet.jit.si (since October 2026) |
| Open source | no, extensible with plugins | yes |
| Recording, live streaming, phone dial-in | recording in your own browser only | yes (depending on installation) |
As of October 2026, information about Jitsi based on its public documentation.
The core difference: media server or direct connection
Jitsi sends everybody’s video and audio to the videobridge, a media server that distributes the streams to everyone else. That is efficient and allows large meetings. The price: transport encryption ends at the bridge, which decrypts the media and encrypts it again. Jitsi additionally offers true end-to-end encryption, but the moderator has to turn it on per meeting, everyone needs a supported browser, and some features such as server-side recording are unavailable while it is on.
Briefing connects the participants directly. There is no media server where everything comes together. Video and audio are encrypted between the browsers with DTLS-SRTP; chat, files, documents and the connection setup are additionally encrypted with a room key that only the link knows. This encryption cannot be turned off - there is no switch anyone could forget.
No login, not even for the host
On the public meet.jit.si server, the person starting a meeting now has to sign in with a Google or GitHub account. That has curbed abuse, but it also means whoever opens a room is tied to a big platform account.
In Briefing nobody needs an account. What keeps uninvited guests out is not a login but the key in the link: without it, a room can be neither found nor entered. The server does not even know the room’s name.
Who gets in?
In Jitsi the server decides who enters a room; it enforces lobby and room password. In Briefing the participants decide: a newcomer is admitted only if those already inside can decrypt their join message with the room key. A tampered server that lets someone in anyway gains nothing - without the key there is nothing to read.
If you want to be certain, compare the safety codes: six symbols per connection, derived from the certificates the browsers actually use. If someone sits in between, they differ.
Easier to self-host
Both can be self-hosted. A Jitsi installation consists of several services (web server, the Prosody XMPP server, Jicofo, videobridge) and needs plenty of server bandwidth for many participants. Briefing is a single Docker image. Since media does not pass through the server, it gets by with very few resources - the server only helps participants find each other. A running call even survives a server restart.
When Jitsi is the better choice
- Large meetings. Thanks to the videobridge, Jitsi handles meetings too large for direct connections.
- Recording and live streaming (Jibri) as well as phone dial-in (Jigasi).
- Breakout rooms and extensive moderation features.
- Established integrations, for example in learning platforms and chat tools.
- Open source. You can inspect and change the code yourself.
When Briefing is the better choice
- You are a small group and want to talk confidentially.
- Nobody should have to sign in - not even whoever opens the room.
- You want end-to-end encryption without compromises and without having to remember it.
- You want to run a video chat yourself without maintaining media server infrastructure.
- Your calls should run as long as they need, without a time limit.
More comparisons: Briefing compared. The technology in detail: How Briefing works.