Briefing

Open-source P2P video conferencing, honestly reviewed. No marketing copy, just what you actually get.

TL;DR

• What it is: Browser-based, peer-to-peer video group chat using WebRTC — no accounts, no cookies, no server-side recording [README][1].
• Who it’s for: Privacy-conscious individuals, small teams, and developers who want a zero-friction video room they can spin up in seconds or self-host and embed in their own product [README][1].
• Cost savings: Zoom charges $15.99–$19.99/mo per host; Whereby starts at $6.99/mo per room. Briefing self-hosted runs on any $5–10/mo VPS. The hosted version at brie.fi/ng is entirely free [README].
• Key strength: Genuinely zero friction — generate a room link, share it, connect. No account, no app install, no waiting room configuration [1].
• Key weakness: Single-developer project with 1,609 GitHub stars. Limited third-party review coverage, audio quality has been flagged as “over-compressed” by at least one user, and several v1 features (background blur, desktop clients) were deprecated and not replaced [README][1].

---

What is Briefing

Briefing is a WebRTC-based video group chat built by Dirk Holtwick, an independent developer based in Germany. The full hosted product lives at brie.fi/ng. You visit the URL, a random room is created, you share the link, and the other person joins. There is no account creation, no cookie consent wall, and no app download [README][1].

The technology underneath is standard WebRTC — the same browser API that powers Google Meet and Whereby — but the architecture is different. Briefing establishes a direct peer-to-peer connection between participants for video and audio. The server handles only signaling (coordinating the connection setup) via Zerva, a reliable signaling library the author wrote to replace socket.io [README]. Once the call is connected, media flows directly between browsers, not through a relay server.

The project has been running since 2020 (added to AlternativeTo in April 2020 [1]) and is now on version 3.0, which completed a full migration to Vue3 and TypeScript. GitHub shows 1,617 stars and 261 forks as of late 2025 [1], with the project actively maintained. There’s also a free iOS app on the App Store, though the Android, Windows, and Electron builds from v1 were deprecated [README].

The license is AGPL-3.0, meaning self-hosted use is free but if you modify Briefing and deploy it as a network service, you must publish your source changes. A commercial license is available for whitelabeling — contact license@holtwick.de — but pricing is not published [README].

---

Why People Choose It

The third-party review landscape for Briefing is thin. Only one substantive source exists among those reviewed for this article — the AlternativeTo listing [1] — which aggregates community comments. The tool doesn’t appear in major tech media reviews, G2, or Trustpilot. That’s worth naming directly: this is a niche, single-developer tool with a loyal but small community, not a funded startup with a content marketing budget.

From the comments that do exist [1]:

“Free, open source, and P2P” — the recurring headline. Multiple users list these three properties as the entire reason they chose it.

“No sign up needed, not google or microsoft affiliation” — the anti-surveillance angle. For anyone tired of being in Google’s ecosystem even for a five-minute call, this matters [1].

“Ridiculously friction free” — the UX win. The zero-registration, click-link-and-talk experience is genuinely rare. Most video tools require at least an account on one side [1].

“The audio was a bit over-compressed” — one user explicitly flagged audio quality as below expectations, though the overall AlternativeTo rating is 4.8/5 from 5 reviews [1]. With a small sample size that rating means less than it looks.

The tool appears in community lists focused on degoogling, privacy, and anonymous communication — not enterprise video conferencing lists. That placement tells you exactly who the real audience is.

---

Features

Based on the README and the AlternativeTo feature list [1]:

Core:

• WebRTC P2P video and audio — direct browser-to-browser, no media relay [README]
• Text chat in-call [README]
• Screen/desktop sharing [README]
• Simple room links — generate a URL, share it, anyone with the link joins [README]
• No registration, no cookies, no tracking [1]
• E2E encrypted media via WebRTC’s built-in DTLS-SRTP [1]
• Works in all modern browsers, no plugin or app required [README]
• Free iOS app [README]

Self-host / embed:

• Docker deployment [README]
• Embed via iframe with a visual configurator at brie.fi/ng/embed-demo [README]
• Deployable on fly.io, render.com, AWS, GCP, Azure — any Docker host [README]
• Source-level customization for developers comfortable with Vue3/TypeScript [README]

What it doesn’t have:

• Meeting recording — not mentioned anywhere in the README or site
• Calendar integration or scheduling
• Waiting rooms or host controls (standard security-theater features)
• Background blur or virtual backgrounds — these were in v1 and explicitly deprecated [README]
• Dial-in / PSTN access
• Persistent rooms with passwords or lobby settings (rooms are ephemeral by link)
• Admin dashboard for managing users or rooms

The feature list is intentionally minimal. This is a tool that does one thing: secure P2P video via a URL. If your list of required features extends beyond “video, audio, screen share, text chat,” you’ll hit walls quickly.

---

Pricing: SaaS vs Self-Hosted Math

Briefing hosted (brie.fi/ng):

• Free, no tiers, no limits published [README][website]
• The author funds development via GitHub sponsorship and commercial license sales

Briefing self-hosted:

• AGPL-3.0: $0 for software [README]
• VPS to run it: $5–10/mo (Hetzner, DigitalOcean, Vultr)
• Total: ~$60–120/year for infrastructure you own

Commercial license (whitelabeling):

• Pricing not published — contact license@holtwick.de [README]
• Required if you embed Briefing in a closed-source product or SaaS

What you’re replacing:

Service	Cost	Key limit
Zoom Pro	$15.99/mo per host	100 participants
Whereby	$6.99/mo per room	100 participants
Google Meet	Free (with Google account)	100 participants, 60 min on free
Jitsi Meet self-hosted	$5–15/mo VPS	Unlimited
Briefing self-hosted	$5–10/mo VPS	Unlimited (WebRTC limits apply)

The math for pure cost savings isn’t dramatic because Briefing’s SaaS version is already free. The real case for self-hosting is data sovereignty — your signaling server, your logs (none by default), your infrastructure. If you’re connecting with clients or discussing sensitive business matters and you don’t want any third-party server in the path, self-hosting Briefing means the only infrastructure you depend on is your own.

---

Deployment Reality Check

The README points to three paths: Docker, fly.io, and render.com [README].

What the Docker path requires:

• A Linux VPS (1 GB RAM is likely sufficient — the app is lightweight; there’s no media relay)
• Docker and docker-compose
• A domain name and HTTPS (Let’s Encrypt via Caddy or nginx)
• No database required — Briefing is stateless by design

What’s actually bundled: The README says “batteries included” — the app ships with its own signaling (Zerva) and STUN server. You don’t need to configure a separate Coturn/TURN server for the basic case, though a TURN relay is needed for participants behind strict NAT or firewalls (some corporate networks block direct P2P WebRTC) [README]. This is a common WebRTC caveat that isn’t surfaced prominently in the docs.

Time estimate:

• Technical user with Docker experience: 20–40 minutes to a working HTTPS instance
• Non-technical founder following a guide: 2–4 hours including domain setup; the Docker path is simpler than most self-hosted tools because there’s no database or persistent state to configure

What can go sideways:

• Corporate firewall / strict NAT environments will break P2P WebRTC without a TURN relay — Briefing’s bundled STUN helps with NAT traversal but STUN alone won’t punch through symmetric NAT. No TURN solution is documented out of the box.
• The iOS app hasn’t been updated since March 21, 2021 [1] — for mobile-heavy use cases this is a concern
• 21 open issues on GitHub as of late 2025 [1] — typical for a one-developer project; don’t expect enterprise-level SLA on bug resolution
• The embed configurator is a nice touch for integration, but iframe-embedded video calls have known limitations in some browsers

---

Pros and Cons

Pros

• Zero friction, zero account. Click link, start call. No sign-in flow on either side. No app download. This is genuinely rare [1].
• True P2P. Media doesn’t touch a relay server under normal network conditions — privacy by architecture, not just policy [README][1].
• No cookies, no tracking. The hosted version is explicitly designed to store as little data as possible [README][1].
• Browser-native. Works on any modern browser. No WebRTC plugin, no Electron app required [README].
• Free hosted option. brie.fi/ng is free with no account, which means you can use the product without any infrastructure commitment [README].
• Embeddable. iframe embed with a visual configurator makes adding it to your own product feasible without touching code [README].
• Docker + fly.io + render.com. Deployment options cover the main self-host platforms [README].
• Vue3 + TypeScript codebase is modern and extensible for developers [README].

Cons

• Single-developer project. Dirk Holtwick is the sole maintainer. No company, no funding round, no team. This is a sustainability risk for anything mission-critical [README].
• Audio quality concerns. At least one user reported over-compressed audio [1]. With only 5 AlternativeTo reviews, this can’t be statistically dismissed.
• Deprecated features not replaced. Background blur, virtual backgrounds, Android/Windows/Electron apps — all in v1, all removed in v2. If you’re relying on these, they’re gone [README].
• No TURN documentation. WebRTC without TURN fails for users behind corporate firewalls or symmetric NAT. Briefing bundles STUN but the TURN situation isn’t clearly addressed in the README.
• iOS app stuck in 2021. Last App Store update was March 21, 2021 [1] — three-plus years of iOS evolution without an update is a red flag for mobile users.
• No recording, no scheduling, no admin controls. Missing the features that organizations often need around a video tool.
• AGPL-3.0 license. Free for self-hosting, but if you want to embed Briefing in a closed-source SaaS you need the commercial license (pricing unpublished) [README].
• Minimal third-party validation. No G2, no Trustpilot, almost no tech press coverage. Harder to evaluate at scale.

---

Who Should Use This / Who Shouldn’t

Use Briefing if:

• You need an ad-hoc secure video call and don’t want either party to create an account. Send a link, done.
• You’re building a product and want to embed a lightweight video room via iframe without negotiating API pricing with Whereby or Daily.co.
• You’re a privacy-focused individual or journalist who wants calls that don’t touch Google or Microsoft infrastructure.
• You’re already comfortable with Docker and want to self-host a stateless, low-maintenance video tool for a small team.
• You want to test a “bring your own server” video call before committing to something more complex like Jitsi Meet.

Skip it (pick Jitsi Meet instead) if:

• You need enterprise features: recording, live streaming, breakout rooms, meeting scheduling, dial-in.
• You have more than 4–6 participants regularly — WebRTC mesh (everyone sends to everyone) degrades at scale without a selective forwarding unit (SFU). Jitsi Meet includes Jitsi Videobridge (an SFU) for this exact reason.
• You need a mobile app that’s actively maintained.

Skip it (stay on Whereby/Zoom) if:

• Your team is non-technical and needs reliability guarantees, support SLAs, and an admin console.
• Compliance (HIPAA, SOC 2) is a requirement — Briefing has no published compliance certifications.
• You need recordings, transcripts, or integrations with Slack, Notion, or your CRM.

Skip it (pick Element/Matrix) if:

• You want persistent rooms with federation across organizations, not just ephemeral sessions.

---

Alternatives Worth Considering

• Jitsi Meet — the most direct open-source comparison. Self-hostable, also WebRTC-based, also free. Includes an SFU for larger calls, recording via Jibri, and an actively maintained mobile app. More complex to self-host but substantially more capable. 20K+ GitHub stars vs. Briefing’s 1,609.
• Whereby — fully managed, no self-host, clean UI, embeddable. $6.99/mo per room. Good if you want the embeddability without managing infrastructure.
• Daily.co — developer-focused API with 10,000 free minutes/month. More flexible but more complex to integrate.
• Google Meet — free with a Google account, 100 participants, 60-minute limit on free tier. Easy but you’re in Google’s data model.
• Zoom — $15.99/mo per host, 100 participants, most widely recognized in enterprise. Closed source, proprietary, expensive at scale.
• Element (Matrix) — open-source, federated, self-hostable. Better for persistent team communication with video rooms than for ad-hoc calls.

For a non-technical founder who wants to escape Zoom billing: the realistic shortlist is Briefing vs Jitsi Meet. Pick Briefing if you want zero-configuration, link-and-go simplicity and you’re dealing with small groups (2–4 people). Pick Jitsi Meet if you need larger calls, recording, or a maintained mobile app — at the cost of a more involved self-host setup.

---

Bottom Line

Briefing is a well-executed, intentionally minimal tool that does one thing: get two to several people on an encrypted video call in under ten seconds with no account required. For that specific use case, it’s hard to beat. The P2P architecture, zero-cookie design, and free hosted option are genuine differentiators — and for developers, the iframe embed path and AGPL-licensed codebase make it a reasonable choice for lightweight video integration.

The limits are real: single developer, five-year-old iOS app, no TURN documentation, no recording, no admin features, and audio quality that at least one user has flagged. If you’re evaluating it for anything beyond ad-hoc secure calls or a simple embed, you’ll likely run into a missing feature within the first week. Jitsi Meet has more horsepower; Whereby has more polish and SLAs. But for a solo founder who wants to say “here’s a video link” without sending someone through a Zoom account creation flow, brie.fi/ng opens in a tab and works immediately — and that’s the entire value proposition.

If self-hosting is the goal but the Docker setup feels like too much overhead, upready.dev deploys tools like this for clients as a one-time service.

---

Sources

1. AlternativeTo — Briefing listing (5 reviews, 4.8/5 avg; 29 likes; 163 alternatives). https://alternativeto.net/software/brie-fi-ng/about/

Primary sources:

• GitHub repository and README: https://github.com/holtwick/briefing (1,609 stars, AGPL-3.0, maintained by Dirk Holtwick)
• Official website and hosted app: https://brie.fi/ng
• iOS App Store listing: https://apps.apple.com/app/briefing-video-chat/id1510803601
• Embed configurator: https://brie.fi/ng/embed-demo