Does self-hosted Jitsi cost less than Zoom licensing?
Renewal quotes from Zoom are usually the trigger for this question, so the honest answer comes first: Jitsi Meet is Apache-2.0 licensed, so there is no license fee, but the recurring cost does not disappear. It moves into servers, bandwidth, TURN relay capacity, recording storage and the people who build and run the system. A fair comparison therefore sets your current per-user subscription against those components, not against zero. Jitsi is maintained by 8x8, Inc., which also sells hosted Jitsi as a Service, so a managed option is a second cost point to price alongside self-hosting.
Self-hosting tends to cost less when meeting volume is large and steady, when many concurrent participants share the same videobridges, and when data residency rules make an on-premises or sovereign deployment a requirement you would otherwise pay a premium to meet. It tends to cost more for small teams with occasional meetings, for webinars that need extra capacity, for recording-heavy use where Jibri instances and storage grow quickly, and for organizations without staff who can operate Prosody, Jicofo and Jitsi Videobridge. The Jitsi scalable setup guide suggests a 4 CPU, 8 GB machine for the central server and 4 or 8 CPU with 8 GB RAM for each videobridge, which is a starting point for sizing, not a cost estimate. Ask your team to model peak concurrent users, recording hours and bandwidth before comparing totals.
When you request quotes, ask implementation partners and your own infrastructure team to split the figures into one-time work (planning, deployment, hardening, integration with your identity provider, and migration of existing recordings) and recurring work (cloud or data center capacity, egress bandwidth, TURN hosting, storage retention, upgrades, monitoring and on-call support). Ask whether the quote covers HTTPS certificate management, since Jitsi's handbook states that HTTPS is necessary for multimedia to work. Compare that total against your Zoom renewal over the same period and include the internal hours that your staff will spend, because those hours are often the largest line in a self-hosted budget.
Which cost components move when you leave Zoom
This table sets each Zoom cost component against its self-hosted Jitsi equivalent, showing who is paid, whether the cost is one-time or recurring, and what drives it. Read it as a checklist for building a like-for-like quote, since the license line drops out but several infrastructure and staff lines take its place. The main takeaway is that the saving depends on the servers, bandwidth, recording storage and people you already own or would have to buy.
| Cost component | Zoom (commercial side) | Self-hosted Jitsi (your side) |
|---|---|---|
| Subscription or license | Per-user plan or add-on fees, billed on a recurring cycle. Confirm current terms on Zoom's price list and contract. | Jitsi Meet is Apache-2.0 licensed, so there is no license fee. Recurring cost moves to infrastructure and staff. |
| Compute servers | Included in the Zoom service. No servers to buy or run. | Recurring cloud or data center cost for the web, Prosody, Jicofo and videobridge hosts, sized to peak concurrent users. |
| Bandwidth | Included in the subscription, within plan limits. Confirm any overage terms with Zoom. | Recurring egress and ingress charges from your provider, driven by participant count and video quality. |
| TURN and firewall access | Handled by Zoom's cloud and client connectivity. | Usually a one-time design effort plus recurring hosting for a TURN relay, and open ports 80, 443, 10000/UDP and 5349/TCP for TCP fallback. |
| Recording storage | Cloud recordings are stored in Zoom's cloud under your plan limits, and exported as MP4, M4A, TXT, VTT and CC.VTT files. | Recurring disk or object storage for Jibri recordings, which are one recording per Jibri instance. Plan capacity before rollout. |
| Implementation | Typically limited to admin setup, SSO and device rollout by your own team. | One-time effort for DNS, HTTPS certificates, Docker or package install, authentication (JWT or LDAP) and integrations. Ask for a fixed-scope written plan. |
| Migration of existing recordings | Recordings can be downloaded from Zoom's recordings page before the account changes or ends. | One-time effort to download, verify, store and index archived files, plus any retention or legal hold checks. |
| Support, upgrades and internal skills | Vendor support is included in the plan tier you buy. | Recurring staff time or a retainer for patching, monitoring, upgrades and incident response. Confirm the staffing model in your quote. |
What moves the Jitsi cost comparison up or down
Jitsi has no license fee, so the comparison with Zoom turns on the infrastructure and people needed to run meetings at your peak load. The drivers below decide how much compute, bandwidth, recording storage and staff time a self-hosted deployment consumes, and each one should be sized from your own usage data rather than from a generic estimate.
Concurrent participants and peak size
Cost starts with the largest meeting you must support and how many run at once. Jitsi Videobridge is the media router that carries the video, and the Jitsi scalable setup guide describes adding videobridges horizontally as load grows, with the default install already configured for that. Each extra bridge is another server to pay for, patch and monitor. Ask your team for the peak concurrent participant count from your Zoom usage reports, and confirm whether that peak occurs in a few hours a week or is constant.
Recording and streaming volume
Jibri records and streams Jitsi meetings, and each Jibri instance handles one recording at a time, so recording demand adds a separate pool of servers. Storage for recordings also recurs every month and grows with retention periods. Zoom bundles cloud recording into its plans, so this cost often appears only after migration. Estimate how many hours you record each month, how long files stay online, and whether you need a transcription service on top.
SIP dial-in through Jigasi
If users join meetings by phone, Jigasi acts as the SIP gateway that bridges telephone callers into Jitsi rooms. Its cost depends on the number of concurrent dial-in callers and on the telephony provider or SIP trunk you buy, which is billed separately from the software. Zoom dial-in is usually part of a paid plan or an add-on, so compare like with like. Ask your telephony provider for per-minute and concurrent-channel terms before you size the Jigasi capacity.
Availability and redundancy expectations
A single Jitsi server is cheap, but a meeting service that staff rely on for daily work usually needs a second site, standby components and tested backups. Each redundant component doubles some part of the bill and adds monitoring and failover testing. Decide your recovery target before choosing the design. Hosted Zoom carries its own uptime commitments, so confirm the availability terms in your Zoom agreement and ask your team what outage length is acceptable.
Zoom edition and feature choices
The Zoom plan you leave decides what must be rebuilt. Plans with webinars, larger meeting limits, advanced admin controls, or SSO and reporting add-ons each map to a separate Jitsi capability or to a third-party tool. Some features, such as Zoom Node for on-premises use, have no direct Jitsi equivalent. List the features your users actually use from your Zoom admin console, then price the replacement for each, rather than assuming a like-for-like plan.
In-house skills and operations staff
Staff time is often the largest recurring cost in a self-hosted deployment. Someone must patch the operating system and containers, renew certificates, tune the videobridges, handle TURN and firewall rules, and respond to incidents. Teams without that skill set either hire, train or buy implementation and support. Ask whether your platform engineers already run Docker, Linux and TLS at this scale, and what hours they can spare each month for the service.
How to build the comparison with your own numbers
This sequence turns Zoom's per-user invoice into a cost model built from your own license counts, meeting minutes, peak concurrency and recording volume, so the comparison with self-hosted Jitsi reflects your environment rather than general assumptions.
Export current Zoom licenses and plan features
The Zoom administrator lists every licensed user, the plan each one holds, add-on licenses such as webinar or cloud recording capacity, and the admin features your organization depends on, including SSO, reporting and integrations. Finance confirms the annual contract value and renewal date from the Zoom order form. Done when you have a single sheet with license counts by plan and a list of features that must exist after migration, which becomes the scope baseline for Jitsi.
Inventory meeting minutes and peak concurrency
Pull meeting usage reports from the Zoom admin portal for the last full year, covering monthly participant minutes, the busiest days and the highest number of simultaneous meetings and participants. Note which teams hold the largest and longest sessions, such as webinars, training or external calls. Done when you have a monthly minutes figure and a peak concurrency figure that you can later use to size videobridges.
Measure recording and transcript volume
Count cloud recordings by year and total their storage size, separating MP4 video, M4A audio, chat text, VTT transcripts and CC.VTT captions. Identify which recordings must be kept for legal, training or records-retention reasons. Done when you have a total terabytes figure, a retention list and an estimate of how many Jibri recordings or BigBlueButton archives the new platform must hold. Confirm the recording formats in Zoom's support article before you plan storage.
Archive existing Zoom recordings before exit
Download every recording you must keep before the Zoom contract ends and before any cloud retention window closes. Store the MP4, M4A, TXT, VTT and CC.VTT files in your own object storage or file archive, and record where each meeting's files now sit. Ask your Zoom admin to confirm that downloads are complete for each user. Done when an inventory matches the archive count and a restore test opens sample files, because recordings left in Zoom are not carried over to Jitsi automatically.
Size Jitsi components from the supplied minimums
Using the peak concurrency figure, plan one central server at no less than 4 CPU and 8 GB of memory, and plan each videobridge at 4 or 8 CPU with 8 GB of RAM, adding videobridges as concurrency grows, since the Jitsi scalable setup guide says the default install supports horizontal scaling. Add separate planning for the recording machine if Jibri is needed, since one recording runs per Jibri instance. Done when you have a bill of materials per environment, including production and a test system, that a platform engineer has reviewed.
Add TURN, certificates and storage costs
List the components that are easy to forget: a TURN relay for users behind restrictive firewalls, a publicly trusted HTTPS certificate with a proper domain (the Jitsi handbook warns that self-signed certificates cause problems, especially on mobile), outbound and inbound network capacity on UDP port 10000 and the other required ports, backups, monitoring and recording storage. Ask your network team to confirm firewall and bandwidth needs for your sites. Done when each item has an owner, a unit cost source and a note on whether it is a one-time or recurring expense.
Price each component and assign staff hours
Obtain unit prices for cloud or data center capacity, bandwidth, TURN hosting, certificates, storage and backup from your own vendors, and separate these recurring costs from one-time items such as design, installation and integration with your identity provider. Estimate the platform engineering, security and help desk hours the service will consume each month, based on your team's own rates. Done when you have a total cost of ownership table for three years that shows each line, its source and its owner, alongside the Zoom license total.
Request fixed-scope quotes from implementation partners
Send the bill of materials, the feature list from step one, the archive plan and the security and identity requirements to two or more implementation partners, and ask each for a written quote against a fixed scope with deliverables and timelines agreed before work starts. Ask them to separate implementation, hardening, backup, training, documentation and any retainer for ongoing support and upgrades. Done when the quotes are comparable line by line, and you can show the board a side-by-side view of Zoom renewal cost against the self-hosted total.
Where the Jitsi running cost comes from
The license fee for Jitsi Meet is zero, but the running cost sits in the components you operate. A self-hosted deployment is made of the web front end, the Prosody XMPP server, Jicofo, and one or more Jitsi Videobridge media routers. Prosody, Jicofo and the web server form the control plane, which is small and runs on one central machine. The videobridges carry the audio and video, so they are the part that grows with participants and drives bandwidth and compute spend. Optional Jibri (recording and streaming) and Jigasi (SIP) add their own hosts and their own traffic, so decide early whether you need them, because each adds recurring infrastructure and support work. The Jitsi handbook describes the scalable setup, and the videobridge sizing it suggests is the starting point for your capacity estimate.
Every Jitsi deployment needs a valid HTTPS certificate on a proper domain name. The Jitsi handbook states that HTTPS is necessary for audio and video to work, and it warns that self-signed certificates cause problems, especially with mobile clients. Plan for a certificate renewal process on your side, whether that is an internal certificate authority or a public one, and budget time for the first mobile test rollout, since a browser warning that users click through can still break a phone client. Ports are part of the same planning exercise: 80/TCP and 443/TCP for the web app, 10000/UDP for media, with 5349/TCP as a TCP fallback and 3478/UDP for STUN as optional items. Confirm each port against your firewall and network policy before the pilot.
Operations effort also depends on how you run the containers. Since release stable-11146, the official Docker setup runs rootless with read-only filesystems. That improves the security posture, but it changes what your operators can change inside a running container, so ask your engineers to test upgrades, custom configuration and any Jibri or Jigasi changes in a staging environment first. Confirm with your platform team whether they already run rootless containers, because that determines whether the work is routine or a new skill to build. Budget this as recurring operations time for patching, upgrades and monitoring, not as a one-time installation task.
What the migration adds to the one-time bill
The one-time bill for leaving Zoom is more than the server build. Before any Jitsi server goes live, someone has to export what Zoom holds. Cloud recordings can be downloaded as MP4 video, M4A audio, TXT chat, VTT transcript and CC.VTT caption files, as described in Zoom's recording file format article. Confirm with your own team how many hours of recordings exist, who owns them, and how long they must be retained, because that sets the storage and staff time for the export and for any archive you build on your own servers.
Rebuilding the meeting layer is labor that rarely appears on a Zoom invoice. Each recurring meeting link, personal room, calendar integration and SSO login has to be recreated against your Jitsi domain. Jitsi's authentication options are configured in the .env file, and the handbook recommends JWT token authentication with a separate anonymous domain for guests. Someone must decide which users get accounts, who issues tokens, and how identities map from your directory. Those decisions and the configuration work belong in the one-time scope, and they should be written into a fixed-scope statement before work starts.
Rollout, parallel running and training finish the bill. A dual-running period means you pay for Zoom licenses and the self-hosted servers, staff time and bandwidth at the same time. The length of that period is a planning decision, not a fact we can supply. Set it with your team by agreeing exit criteria, such as which meeting types have moved and which integrations have been verified. Training for hosts, moderators and help desk staff, plus updated guidance on recording consent, also falls in this phase. Ask any implementation partner to price these items separately in the written scope.
Questions buyers ask before comparing costs
How much does self-hosted Jitsi cost compared with Zoom?
Jitsi Meet has no license fee, so the cost is what you pay for infrastructure, people and support. Zoom bills per user on a subscription, so its cost grows with headcount and add-ons. Self-hosted Jitsi costs recur mainly in servers or cloud instances for the web front end, Prosody, Jicofo and Jitsi Videobridge, bandwidth for media, a TURN server for users behind strict firewalls, and storage and compute if you add Jibri recording. One-time costs include design, deployment and hardening. Ask any quote to separate these components so you can compare them line by line with your Zoom renewal, and model peak concurrent meetings, not total users.
How many staff does self-hosted Jitsi need, and can our IT team run it alone?
Most teams can operate Jitsi with existing Linux and networking skills, but someone must own it. Staffing depends on how many meetings run at once, how often you patch, whether you run recording or SIP, and how fast you must respond to outages. Your team needs skills in Linux administration, DNS, TLS certificates, firewalls, Docker or Debian packaging, and basic monitoring. Ask whether the work fits into existing duties as a fraction of one role, or needs a dedicated on-call rotation. Operations staff time is usually the largest recurring cost, so account for it explicitly in your comparison.
How long does a Jitsi implementation take, and what drives the timeline?
The timeline depends on scope, not on the software itself. The main drivers are the number of environments, whether you integrate with identity providers such as LDAP or JWT-based login, whether recording through Jibri or dial-in through Jigasi is required, how many videobridges you need to scale, and how long your change board takes to approve production. Network and certificate work often takes longer than the install. Implementation is usually fixed-scope, so the scope, deliverables and dates are agreed in writing before work starts. Ask for a written plan that lists each dependency.
What does the work need from us, such as domains, certificates, network access and sign-off?
You will need to provide several items before deployment starts:
- A domain name for the meeting service and a valid, publicly trusted certificate for it. The Jitsi handbook says HTTPS is necessary for audio and video, and self-signed certificates cause problems, especially on mobile.
- Firewall rules for ports 80 and 443 over TCP, and 10000 over UDP for media. Confirm whether 5349 over TCP and 3478 over UDP are required for your users.
- Access to your cloud account or data center, and a named owner for DNS and certificate renewal.
- Decisions on authentication, such as JWT tokens, LDAP or Matrix verification, and on who may create rooms.
- A sign-off process for test results, backup procedures and go-live.
Confirm each item with your network and security teams early.
Can we do the Jitsi deployment ourselves, and what do we lose?
Yes, Jitsi is designed to be self-hosted, and the handbook covers Docker and Debian or Ubuntu packages. You keep full control of data, upgrades and configuration, and you avoid a vendor contract. What you give up is speed of expertise and an external party accountable for the result. Internal teams often underestimate hardening, backup testing, load testing and the first major upgrade. If you go alone, plan for a test environment, a rollback path and a named owner. Many organizations split the work, keeping day-to-day operations in house while buying a fixed-scope implementation for the initial build.
Does Jitsi need a license fee, and what does Apache-2.0 allow?
Jitsi Meet is licensed under Apache 2.0, according to its GitHub repository, so there is no license fee for self-hosting. Apache 2.0 allows you to use, modify, distribute and run the software commercially, and it includes a patent grant, subject to its conditions such as keeping license notices. The name Jitsi is a trademark of 8x8, Inc., so check trademark terms if you rebrand or redistribute. Hosted services such as Jitsi as a Service, offered by 8x8, are a separate commercial purchase. Have your legal team confirm obligations for your specific use.
When is BigBlueButton the better cost choice than Jitsi?
BigBlueButton is usually the better fit when meetings are structured sessions such as classes, training or webinars that need a whiteboard, shared notes, polling and breakout rooms, especially inside an LMS. Its cost profile is heavier: BigBlueButton 4.0 needs at least 16 GB of memory, 8 CPU cores, 500 GB of disk for recordings and 250 Mbit/s of symmetrical bandwidth, according to its install documentation. It also requires a clean server install for 4.0 and does not support direct upgrades from 2.6, 2.7 or 3.0. Jitsi is often cheaper per meeting for ad hoc calls. Model both against your actual meeting pattern.
When the numbers favor staying on Zoom
Staying on Zoom, or moving only the rooms that need a different setup to Zoom Node, is often the cheaper and simpler choice when the self-hosting case is weak. Self-hosted Jitsi removes the per-user license line, but it replaces that line with recurring infrastructure and staff time. With a small user base, low meeting volume and no residency driver, that trade rarely pays off. Ask your team to count active hosts over a normal month, the peak number of concurrent participants, and the hours each week that someone in IT would spend patching the web front end, Prosody, Jicofo and Jitsi Videobridge. If the answer is a handful of users and a few hours of meetings, a hosted subscription usually carries less operational risk.
The same reasoning applies when no one on your team can run the stack. A Jitsi deployment needs TLS with a proper domain certificate, since the Jitsi handbook says HTTPS is necessary for audio and video to work, plus firewall rules for the media ports and a plan for scaling videobridges. BigBlueButton adds a much heavier server specification and a clean install for each major release. If you cannot staff those tasks, or pay an implementation partner to own them, the labor line can exceed the license savings. Confirm the skills you actually have before you model the cost.
Zoom Node deserves its own check. It keeps meeting traffic on premises, yet it is managed and updated from the Zoom cloud, so it may satisfy a locality requirement without moving operations in-house. Also weigh integrations. If your calendars, LMS plugins, room systems or reporting depend on Zoom-specific APIs and vendor add-ons, rebuilding them is a real cost that does not show up on a license invoice. Document every integration in use, then ask each replacement vendor to confirm the equivalent. Staying on Zoom remains a defensible answer when those dependencies are deep and the self-hosting drivers are absent.
How DeployOpen scopes a fixed-price Jitsi implementation
DeployOpen is a Chainscore Labs company that plans, implements, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a Zoom cost comparison, we start by writing down the full cost of a Jitsi deployment so the decision rests on your numbers.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts
- The written scope lists the Jitsi components to deploy, such as web, Prosody, Jicofo, Jitsi Videobridge, Jibri and Jigasi
- We record the infrastructure you must fund, including servers, bandwidth, TURN and recording storage
- Scoping also covers the Zoom features you use today and which ones move to Jitsi, need add-ons or stay unmet
How we build
- We deploy Jitsi with Docker or Debian and Ubuntu packages, matching the platform your team can operate
- We configure HTTPS with a proper domain certificate, since Jitsi requires it for working audio and video
- We set up authentication, such as JWT tokens with a separate guest domain, in line with Jitsi's current guidance
- We test the deployment with your user counts and network paths before any users are onboarded
How we hand over
- You receive documentation covering the architecture, configuration, sizing assumptions and operating procedures
- Handover includes backup and restore steps for configuration and any recordings you keep on your own storage
- We document the cost model so you can see which items are one-time and which recur each year
- Your staff are trained on routine operation, so you know what to monitor and who handles each task
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Retainers can cover Jitsi version upgrades, which the scope should name with the release cadence you agree
- Support scope, response expectations and service levels are written into the retainer, not assumed
- Ask for a quote built from the written scope, since DeployOpen does not publish a price list
