Jitsi Meet

Open-source video conferencing, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (Apache-2.0) video conferencing platform — think Zoom or Google Meet, but the server lives in your infrastructure and no one raises your bill [1][5].
• Who it’s for: Privacy-first teams, NGOs, open-source communities, educators, and developers who need embeddable video in their own products [1][5].
• Cost savings: Microsoft Teams runs $6–22/user/month as part of Microsoft 365. Zoom Pro is $13.33/user/month. Jitsi self-hosted runs on a $10–20/mo VPS with unlimited participants and no per-seat fees [2].
• Key strength: No account needed. Share a link, everyone joins from a browser. Apache-2.0 license means you can embed, rebrand, and redistribute without calling a lawyer [1][5].
• Key weakness: Recording requires a separate Jibri service that needs its own dedicated machine. Performance degrades noticeably past 15–20 participants on modest hardware. Not a serious option for large-scale enterprise meetings [1][2].

---

What is Jitsi Meet

Jitsi Meet is a browser-based video conferencing platform built on WebRTC. You create a meeting room by naming it (or generating a random URL), share the link, and everyone joins — no app download required, no account required [1][README]. The project is a collection of components: Jitsi Videobridge (the media router), Jicofo (conference coordinator), Prosody (XMPP signaling), and the Meet web app itself [README].

The public instance at meet.jit.si lets anyone test it immediately. The self-hosted path gives you the same experience running inside your own infrastructure, with full control over who can create rooms, who can join, and what happens to your call data [1][2].

The project is maintained by the Jitsi team at 8x8, the enterprise comms company that acquired Jitsi in 2018. It sits at 28,822 GitHub stars as of this review, with an Apache-2.0 license — the same permissive license that lets you fork, white-label, and ship commercially without a separate agreement [README].

8x8 also offers JaaS (Jitsi as a Service) — a managed cloud version that lets you skip the infrastructure entirely while keeping Jitsi branding and APIs. This is the managed path for teams that want Jitsi’s openness without handling Debian packages and STUN/TURN servers [README].

---

Why people choose it over Zoom, Teams, and Google Meet

The pattern across the reviews is consistent: people come to Jitsi for the no-account link sharing and data control, and they stay because the price is zero. The frustrations are equally consistent: it struggles at scale and lacks the polished reliability of paid services.

The privacy argument. MeetingToolsHub [1] puts this at the center of its review: Jitsi offers “transparency through its open-source codebase” and the ability to self-host, keeping call data entirely within your own infrastructure. For NGOs, healthcare organizations, and anyone uncomfortable routing video through Microsoft or Google servers, this matters more than feature parity with Teams [1].

No-friction entry. No account creation, no forced app install, no waiting for IT to provision licenses. You share a URL and the meeting starts [1][5]. CompsMag [5] specifically calls out that Jitsi has no time limits on meetings — most free tiers of competing tools cap meetings at 40–60 minutes. Jitsi on meet.jit.si or self-hosted doesn’t.

Cost at scale. For a team of 25 people, Microsoft Teams via M365 Business Basic runs roughly $150/month. Jitsi on a $15 Hetzner VPS costs $15/month regardless of how many users you have. The math only gets more extreme as headcount grows [2].

The enterprise story is weaker. MeetingToolsHub [1] is explicit: Jitsi is “less reliable at scale and lacks enterprise-grade reliability guarantees, making it unsuitable for large or business-critical meetings.” This isn’t a knock on the software — it’s the honest trade-off between running your own infrastructure and paying someone else to guarantee uptime SLAs [1].

---

Features

Based on the README and third-party reviews:

Core conferencing:

• HD audio and video via WebRTC [README][5]
• Browser-based — no install required for participants [1][README]
• Screen sharing (full screen, application window, or tab) [README][5]
• Mobile apps for Android (Play Store and F-Droid) and iOS [README]
• Raise hand, emoji reactions, polls [README]
• In-meeting chat with private conversations [README]
• Virtual backgrounds [README]
• Customizable meeting URLs [5]
• No time limits [5]

Security:

• End-to-End Encryption (E2EE) available — with a documented caveat: E2EE disables Jibri recording and phone dial-in, since those require server-side access to the media stream [security docs]
• Password-protected rooms via built-in authentication [2]
• JWT token authentication for room access control [2]
• TLS via Let’s Encrypt [2]

Integration and embedding:

• Web SDK and native SDKs for embedding Jitsi video in your own application [README]
• iFrame API for embedding in web pages [README]
• Integrations with Google Calendar, Microsoft Outlook, Slack [5]
• Live streaming to YouTube or Facebook [4]

Recording:

• Jibri service handles recording and streaming — but requires its own dedicated container/machine with a Chrome instance and virtual framebuffer [2]
• Cloud upload via rclone for storing recordings in S3, Google Drive, etc. [2]

What’s notably missing:

• No built-in transcription or AI meeting summaries
• No breakout rooms in the core open-source build (available in JaaS)
• No persistent meeting history or recordings UI without additional setup
• Whiteboard was added recently (v2.7.2 per a WordPress plugin vendor [3])

---

Pricing: SaaS vs self-hosted math

meet.jit.si (public instance):

• Free with no account required [README]
• Suitable for occasional, low-stakes meetings
• Data routes through 8x8’s servers — not appropriate for sensitive calls

JaaS — Jitsi as a Service (8x8’s managed cloud):

• Has a developer free tier [README]
• Paid tiers are usage-based (minutes consumed) — exact pricing at jaas.8x8.vc, data not available in source material
• Handles scaling, TURN servers, and reliability for you

Self-hosted:

• Software license: $0 (Apache-2.0) [README]
• VPS to run it: $10–20/month on Hetzner, Contabo, or equivalent
• Jibri recording requires a separate machine (adds another $10–20/month if needed)
• Your time to deploy and maintain

Competitors for comparison:

• Zoom Pro: ~$13.33/user/month, 100 participants, 30-hour limit per meeting
• Microsoft Teams Essentials: ~$4/user/month standalone; $6/user/month with M365 Business Basic
• Google Meet: included in Google Workspace ($6–18/user/month)

Concrete math for a 20-person team:

Teams at $6/user/month = $120/month = $1,440/year. Zoom Pro for 3 licensed hosts + unlimited attendees runs roughly $40–120/month depending on configuration. Jitsi self-hosted on a $15 VPS with Jibri on another $15 VPS = $30/month = $360/year. Against Teams, that’s roughly $1,000+ saved annually, and the savings compound as headcount grows [2].

The caveat, as always: someone needs to maintain the VPS, renew the TLS certificate, and debug the TURN server when UDP is blocked on a conference hotel’s WiFi. If no one on your team knows what STUN/TURN means, budget for that learning curve or a one-time setup fee.

---

Deployment reality check

The Medium guide by Benjamín Guzmán [2] is the most useful deployment reference available in the source material. The honest summary:

What you need:

• A Linux VPS with at minimum 2 CPUs at 2GHz and 4GB RAM — the 4GB is specifically for running Jibri (recording). Basic conferencing without recording can work on less [2]
• A public IP address (preferred — NAT setups add TURN server complexity) [2]
• A domain name with a valid TLS certificate via Let’s Encrypt [2]
• Docker and docker-compose (the recommended deployment path) [2][README]

The setup steps [2]:

1. SSH hardening and user setup on the VPS
2. SELinux or AppArmor configuration
3. Docker installation
4. Jitsi deployment via the official Docker Compose stack
5. Let’s Encrypt certificate provisioning (staging first, then production)
6. Authentication configuration — internal password-based access or JWT
7. Jibri setup for recording, plus rclone config if you want cloud upload

The guide explicitly warns that commands require customization — don’t blindly copy instructions, adapt the arguments to your environment [2].

What can go sideways:

• TURN server configuration is where most self-hosters hit a wall. If your participants are behind restrictive firewalls, you need a TURN server for UDP/TCP relay. The Docker Compose stack includes coturn, but it requires additional port configuration.
• Jibri is high-maintenance. It runs a headless Chrome browser to capture the meeting stream, which means it can crash, OOM, or behave differently across versions. Expect to restart it occasionally.
• E2EE breaks recording. If you enable E2EE, Jibri stops working. You pick one or the other [security docs].
• Performance degrades fast past 15–20 participants on a modest VPS. The Jitsi Videobridge is selective forwarding (SFU), not mixing, so it’s more efficient than older MCUs — but it still needs CPU per participant. The MeetingToolsHub review [1] is blunt: the platform is “less reliable at scale.”
• Authentication isn’t on by default. The public Docker Compose configuration allows anyone who knows your domain to create a room and start a meeting. Turn on token-based auth or internal authentication before pointing your domain at it [2].

Realistic time estimate: 1–3 hours for an experienced Linux user following a guide. For someone new to VPS management: a full weekend, including debugging. Jibri recording adds another 1–2 hours.

---

Pros and Cons

Pros

• Apache-2.0 license. No strings attached — self-host, embed in your product, rebrand, sell. No “fair-code” restrictions, no commercial use clauses [README].
• No account required for participants. Share a link, they join in a browser. Lowest possible friction for ad-hoc calls [1][5].
• No meeting time limits. Unlike Zoom’s free 40-minute cap or Teams’ restrictions on free tiers [5].
• No per-seat pricing. Once self-hosted, 5 or 500 users costs the same [2].
• E2EE available. One of the few video platforms where server-side access to media is genuinely optional [security docs].
• Embeddable. The iframe API and SDKs are real and used in production by third-party products [README][3][4].
• Mobile apps on all major platforms, including F-Droid for de-Googled Android [README].
• 28,822 GitHub stars with active maintenance by the 8x8 team [README].

Cons

• Not reliable for large meetings. MeetingToolsHub [1] rates it 7.6/10 specifically because of scale limitations and missing enterprise reliability guarantees. If your all-hands has 200 people, this isn’t the tool.
• Recording is painful. Jibri requires its own machine, runs a headless browser, and is genuinely finicky. Most self-hosters skip it or move to JaaS for recording [2].
• E2EE disables recording and dial-in. You can have encryption or recording, not both [security docs].
• Default install is open to the world. Authentication requires explicit configuration — easy to misconfigure [2].
• TURN server complexity. Participants on restricted networks need a TURN relay. Getting coturn working correctly is a common pain point.
• No meeting persistence. No recording dashboard, no meeting history, no participant analytics out of the box.
• Backed by a single company (8x8). The open-source project is real, but the primary maintainer is a commercial entity. If 8x8’s priorities shift, the project’s momentum could too [1].
• UI is functional, not polished. Zoom and Teams have years of UX investment. Jitsi Meet’s interface is clean but feels like open-source software from 2018 that received incremental updates rather than a product-led redesign.

---

Who should use this / who shouldn’t

Use Jitsi Meet if:

• You need a private video conferencing server where your call data doesn’t leave your infrastructure — NGOs, healthcare, legal, or any team with data sovereignty requirements [1].
• You’re embedding video into your own product and need a permissive license that won’t create IP problems [3][4].
• Your team’s needs are simple: ad-hoc calls, screen sharing, basic chat. No meeting history required.
• You’re comfortable with Docker deployment or have someone who is.
• You want unlimited participants and no time limits for a fixed VPS cost rather than per-seat SaaS pricing [2].

Skip it (use Zoom or Teams) if:

• Your meetings regularly have 30+ participants. Zoom’s infrastructure is engineered for this; your Jitsi VPS might not be [1].
• You need reliable recording with cloud storage and a UI to find recordings afterward. Jibri is workable but not production-grade without significant babysitting [2].
• Your participants are non-technical and likely to hit “my video isn’t working” issues that you don’t have time to debug.
• Your compliance team requires audit logs, SSO, and a vendor SLA.

Use JaaS (8x8’s managed Jitsi) if:

• You want Jitsi’s API and embedding capabilities without running the infrastructure yourself [README].
• Recording and scale matter but you like the open ecosystem.

Skip it entirely (pick a hosted alternative) if:

• You have zero Linux experience and no technical help available.

---

Alternatives worth considering

• Zoom — the reliability baseline. Best mobile experience, largest ecosystem of integrations, most recognizable brand. Per-seat pricing adds up fast. Fully closed source.
• Microsoft Teams — the enterprise default. Deep Office 365 integration. Makes sense if your team lives in M365 already; excessive if you don’t.
• Google Meet — included in Google Workspace, reliable, no setup. Closed source, data through Google.
• BigBlueButton — open-source, specifically designed for education, has breakout rooms and whiteboard as first-class features. Significantly harder to self-host than Jitsi.
• Element / Matrix — if the goal is federated, self-hosted communication with video as one part of a broader messaging platform.
• Daily.co — if you’re building video into a product and don’t want to operate the infrastructure, Daily is the commercial embedded video alternative to the Jitsi iframe API.

For a non-technical founder escaping Zoom or Teams bills, the realistic shortlist is Jitsi Meet vs. BigBlueButton. Pick Jitsi if simplicity and ease of deployment matter. Pick BigBlueButton if education use cases and built-in virtual classroom features matter.

---

Bottom line

Jitsi Meet is the most honest answer to “how do I run my own video calls?” — not because it’s the best video conferencing software, but because it’s the only one where that question is genuinely answerable without a commercial agreement. The Apache-2.0 license is real. The browser-based join flow is genuinely frictionless. The cost on a $15 VPS is hard to argue with.

The trade-offs are equally real: recording is a separate service that needs babysitting, performance past 15–20 participants on modest hardware isn’t guaranteed, and the default install requires hardening before it’s actually secure. This is self-hosted software, which means you own the benefits and the operational burden.

For privacy-first teams, NGOs, and developers embedding video into their own products, those trade-offs are worth it. For a 50-person company that needs reliable all-hands calls with automatic recording, Teams or Zoom are the less frustrating choice — and that’s a legitimate answer, not a failure to embrace open source.

If the deployment and maintenance is the blocker, upready.dev sets this up for clients as a one-time service.

---

Sources

1. alwarez21, MeetingToolsHub — “Jitsi Meet Review” (January 3, 2026). https://meetingtoolshub.com/jitsi-meet-review/
2. Benjamín Guzmán, Medium — “Setting up a self-hosted video conference server (Jitsi)” (March 13, 2022; updated September 10, 2023). https://medium.com/@GuzmanBenjamin/set-up-a-self-hosted-video-conference-server-jitsi-383e433f3f06
3. WPPOOL — “Host Meetings Easily with Frontend Creation in Jitsi Meet v2.7.0” (September 17, 2025). https://wppool.dev/host-your-own-meetings-with-frontend-meeting-creation/
4. WPPOOL — “Branded Meetings, Zero Server Hassle — Service”. https://wppool.dev/webinar-and-video-conference-with-jitsi-meet/service/
5. CompsMag — “Jitsi Meet review: Free, open-source video conferencing”. https://www.compsmag.com/reviews/jitsi-meet-review/

Primary sources:

• GitHub repository and README: https://github.com/jitsi/jitsi-meet (28,822 stars, Apache-2.0 license)
• Official public instance: https://meet.jit.si
• JaaS managed cloud: https://jaas.8x8.vc
• Security documentation: https://jitsi.org/security
• E2EE whitepaper: https://jitsi.org/e2ee-whitepaper/
• Deployment handbook: https://jitsi.github.io/handbook/docs/devops-guide/