Is Webex cost vs self-hosted Jitsi cheaper for your organization?
Most organizations reach this comparison after a Webex renewal or a change to pricing or licensing terms. Self-hosted Jitsi removes the per-user subscription, but it adds servers, bandwidth, implementation effort and operations staff. Whether that trade is cheaper depends on your user count, your peak concurrent meeting load and whether your team can run the platform without pulling people off other work. Jitsi Meet is Apache-2.0 licensed, so there is no license fee for the software itself. Every other cost is one you will pay for directly, either to a vendor, a partner or your own staff. Start by pulling your Webex contract figures: the per-user or per-license rate, the term, any Video Mesh or hybrid add-ons, and the renewal uplift. Video Mesh is an extra cost layer if you use it. Its nodes are on-premises Cisco UCS servers that stay registered to the Webex cloud and are managed in Control Hub, so you keep paying for the subscription and for the hardware, while the media stays local. Ask your Cisco account team to separate those line items so you can see what would disappear at cutover and what would remain. On the self-hosted side, the figures you can plan from are the hardware floors. 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, and it notes that the default install is already configured to scale horizontally. For BigBlueButton 4.0, the install documentation calls for at least 16 GB of RAM with swap, 8 CPU cores, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth. Multiply these by your peak concurrency, add redundancy, then request quotes that price cloud or data center capacity, egress bandwidth, and the hours your engineers will spend on upgrades, monitoring and incident response.
Which cost components change when you leave Webex
This table compares each cost component of a Webex deployment with its self-hosted Jitsi equivalent, and marks whether each cost is one-time or recurring. Read it as a checklist for a quote request: the software line drops to zero for Jitsi Meet, but hardware, bandwidth, staff and migration effort move to your own budget. No single figure applies to every organization, so use the rows to decide what to price.
| Cost component | Webex side | Self-hosted Jitsi side | One-time or recurring |
|---|---|---|---|
| Software license or subscription | Per-user Webex subscription, plus any Control Hub or Video Mesh entitlements your contract includes | Jitsi Meet is Apache-2.0 licensed, so there is no license fee. Confirm that any add-ons you plan to use carry no separate terms | Webex: recurring. Jitsi: none for the core software |
| Video Mesh hardware (if used) | Cisco UCS servers on premises, purchased or leased, running Video Mesh software registered to the Webex cloud and managed in Control Hub | Not needed. Jitsi videobridges run on servers you choose, so existing virtual machines or cloud instances may be reused | One-time for purchase, recurring for lease or support. Confirm Cisco hardware terms with your reseller |
| Servers for meetings | Included in the Webex service for cloud meetings; Video Mesh nodes are the only on-premises compute | Central server plus one or more videobridges. The Jitsi scalable setup guide suggests a 4 CPU, 8 GB central server and 4 or 8 CPU, 8 GB videobridges as starting points | Mostly one-time for hardware, recurring for virtual machine or cloud capacity |
| Bandwidth | Cloud meetings use Webex-provided media paths; Video Mesh keeps local media on the LAN and overflows to the cloud when local capacity runs out | Videobridge traffic uses your own WAN links. Confirm upload capacity with the sizing exercise before go-live, since remote participants share it | Recurring for internet and transit; capacity is often already paid for |
| Implementation | Tenant setup, Control Hub configuration, Video Mesh deployment and room device onboarding, usually handled by Cisco or a partner | Design, install, HTTPS certificates, authentication (JWT or other method), SIP gateway setup if used, and testing. Confirm whether recording needs Jibri as a separate server | One-time. Obtain a fixed-scope written quote covering each item |
| Migration of recordings | Recordings are stored in the Webex cloud or on local storage; export options depend on your site configuration. Confirm the export path and formats in writing | Recordings stored on your own storage. Plan storage size, retention rules and a transfer of archived files | One-time for transfer; recurring for storage growth |
| Support and monitoring | Vendor support through the Webex contract, with Cisco handling the cloud service | Your staff or a support retainer covers patching, monitoring, incident response and capacity changes. Ask for response expectations in the scope | Recurring. Retainer or internal time is the main ongoing cost |
| Upgrades and maintenance | Cloud features update on the vendor's schedule; Video Mesh software updates are managed through Control Hub | Your team tests and applies Jitsi releases, plus operating system and Java updates. Budget time for regression testing each cycle | Recurring. Effort varies with release frequency and change control |
| Internal skills | Admins learn Control Hub; fewer infrastructure skills are needed | Linux, networking, TLS, XMPP and container operations. Identify who owns this before the decision, or contract it | Recurring for staff time or retained expertise |
What the hardware and bandwidth lines look like for Jitsi and BigBlueButton
Jitsi and BigBlueButton put very different hardware lines on your budget, so the first decision is which one fits your meeting pattern. A self-hosted Jitsi deployment is split into the web front end, the Prosody XMPP server, Jicofo and one or more Jitsi Videobridge media routers, with optional Jibri for recording and streaming and Jigasi for SIP. 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. Because the default install is already set up for horizontal scaling, capacity grows by adding videobridges rather than by enlarging one machine. Recording with Jibri adds its own hosts, so confirm whether you need it before you size anything.
BigBlueButton 4.0 is a single, heavier server by comparison. The install docs call for at least 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB if you turn recording off) and 250 Mbit/s symmetrical bandwidth. It installs on Ubuntu 24.04 with bbb-install.sh, and the docs recommend a clean server because direct upgrades from 2.6, 2.7 or 3.0 are not supported. Ask your hosting provider or hardware vendor to price a server that meets these minimums, including the symmetrical uplink, which is often the costliest line in a data center or colocation contract.
Recording storage and bandwidth grow with use, not with the server count. Every recorded hour consumes disk on the BigBlueButton server or on your storage backend, and the 500 GB figure is a starting point for recording, not a ceiling. Media bandwidth follows the number of participants and streams, so a session with many webcams will need more uplink than one with slides and audio. Ask your team to measure current meeting hours, average participants per meeting and recording retention, then size disk and bandwidth from those numbers. Hardware prices, cloud instance rates and bandwidth charges vary by vendor, region and contract, so get written quotes from your own suppliers before comparing totals with your Webex subscription.
What moves the Webex versus self-hosted comparison
Six drivers decide whether a Webex contract or a self-hosted Jitsi or BigBlueButton deployment costs more over time. Some push cost up on one side only, while others, such as peak load and availability, raise cost on both sides at once, so model them together rather than one at a time.
Concurrent participants and peak load
Peak concurrency sets how many videobridges or BigBlueButton servers you must run, and it is the main driver of self-hosted hardware and bandwidth. On the Webex side, peak use shows up in license tiers and in cloud capacity for overflow. Ask Webex for its licensing terms for your peak participant count, and measure your real peak over several months before sizing your own servers. The Jitsi scalable setup guide notes that videobridges scale horizontally by adding more.
Recording volume and retention
Recordings drive storage cost on the self-hosted side and sometimes retention or export fees on the Webex side. A BigBlueButton 4.0 server needs 500 GB of disk for recordings, compared with 50 GB without recording, so recording policy is a hardware decision. Estimate hours recorded per month, the retention period your compliance team requires, and whether recordings must move to object storage. Confirm with Webex what export and storage limits apply to your plan.
Video Mesh nodes and their use
Webex Video Mesh runs on on-premises Cisco UCS servers, but each node stays registered to the Webex cloud and is managed in Control Hub. If the nodes are underused, you pay for hardware and support without saving on cloud usage. If they are heavily used, you still depend on Webex licensing and cloud management. Count the nodes you run, their utilization, and whether they would be retired at cutover, because a self-hosted Jitsi deployment replaces those servers rather than adding to them.
Availability and redundancy
Redundancy doubles or triples the self-hosted footprint, since a second videobridge, a standby central server or a second BigBlueButton host adds hardware, bandwidth and monitoring. Webex's cloud carries availability as part of the service, so the self-hosted side adds cost for every redundancy tier you choose. Decide the outage tolerance for meetings and the recovery time for recordings before pricing hardware, and ask Webex to state its availability commitments in writing.
Authentication integration
Single sign-on, directory integration and room authentication add work on both sides. Jitsi supports internal accounts, JWT tokens, LDAP and Matrix verification, and BigBlueButton's Greenlight v3 supports OpenID Connect, often through Keycloak. Connecting to an existing identity provider takes implementation days on the self-hosted side, while Webex often includes these integrations in its license tier. List the identity sources you must connect and check whether your Webex plan includes the same connectors.
In-house operations skills
Self-hosting moves cost from the vendor invoice to staff time: installing, patching, scaling, backing up and troubleshooting media paths such as UDP ports and HTTPS certificates. Webex moves those tasks to the provider, but your team still administers Control Hub and manages user licensing. Compare the hours your staff can give to a video platform with the cost of an implementation partner or a retainer, and ask any partner for a fixed-scope written quote covering installation, handover and ongoing support.
How to build the cost model with your own numbers
This sequence turns the Webex bill and a self-hosted estimate into one comparison over the same term, with every figure traceable to a contract, a quote or a measured usage count.
Collect current Webex and Control Hub costs
Gather the Webex license counts, plan types, add-ons and any Video Mesh or Control Hub charges from the current contract and the latest invoices. The finance team and the Webex account owner usually hold these documents. Record each line as a recurring cost with its billing period, and note the renewal date and any notice terms. The step is done when every line of the current spend can be traced to a signed contract or invoice.
Measure peak concurrency and meeting minutes
Pull usage reports from Control Hub or your Webex administrator for the last several months. Identify peak concurrent participants, total meeting minutes, the share of meetings with more than a few dozen people, and how often recording is used. These figures drive the server and bandwidth sizing in later steps. The step is done when you have a peak concurrency number and a monthly meeting-minute total that the team agrees reflects normal and busy periods.
Size Jitsi or BigBlueButton servers
Map the peak figures to a server plan. For BigBlueButton 4.0, the supplied minimum for one server is 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth. For Jitsi, the Jitsi scalable setup guide suggests a 4 CPU, 8 GB central server and 4 or 8 CPU with 8 GB RAM for each videobridge, and the bridges scale horizontally. Confirm with your architect how many servers your peak needs, and whether you need a separate server for recording. The output is a bill of materials with server count, roles and redundancy choice.
Price bandwidth and storage from your provider
Ask your hosting provider or data center for quotes on the symmetrical bandwidth each server needs, the egress or transfer charges that apply, and the price of recording storage with the retention period your policy sets. Ask whether the price is fixed or metered, and whether backup copies of recordings add to the monthly cost. Cloud and on-premises options should be quoted in the same format. The step is done when each bandwidth and storage line has a provider quote with its unit and billing basis.
Estimate implementation and migration as fixed-scope quotes
Request written, fixed-scope quotes for the build and the cutover. Ask for the scope of the installation, HTTPS and domain setup, authentication integration, SIP or room system work if any, recording archive handling, user communication and testing. A proposal from DeployOpen follows a written scope, so give the same scope to each candidate partner and to internal staff for a like-for-like comparison. The step is done when each one-time cost line is backed by a signed quote or an internal estimate with its assumptions listed.
Add operations staff time for each year
Estimate the recurring staff hours for patching, upgrades, monitoring, backups, capacity changes and user support. Name the people or roles who will do this work and the share of their time it uses. Include on-call coverage if meetings are business critical. Compare this with the support tier you would buy from a vendor or partner if you choose a retainer. The step is done when each recurring labour line names a role, a time share and the source of the rate used to price it.
Compare over one term with costs separated
Build a single sheet covering the same term, for example the length of your current Webex contract. Split costs into one-time items such as implementation, migration and initial hardware, and recurring items such as licenses, hosting, bandwidth, storage and staff time. Show Webex and the self-hosted option side by side, and run a sensitivity check on the largest drivers, such as peak concurrency and recording volume. Every number must come from your contract, quotes or internal records. The sheet is complete when a reviewer can trace each cell to its source document.
Jitsi or BigBlueButton: how the cost profile differs
Jitsi suits day-to-day internal and external meetings where many small calls run in parallel. A self-hosted deployment separates the web front end, Prosody, Jicofo and Jitsi Videobridge, and the Jitsi scalable setup guide notes that videobridges scale horizontally by adding more. The guide suggests a 4 CPU, 8 GB machine for the central server and 4 or 8 CPU with 8 GB RAM for each videobridge, so capacity grows in modest steps rather than through one large machine. Costs fall into a few groups:
- Central server and bridges: Start with one central server and one videobridge, then add bridges as concurrent participants grow. Hardware or cloud instances are the recurring line item.
- Bandwidth: Media traffic is the largest variable cost. Ask your provider for egress pricing per bridge and model it against peak concurrent participants.
- Certificates and DNS: Jitsi requires HTTPS with a proper domain certificate, and self-signed certificates cause problems, especially with mobile clients. Plan for certificate issuance, renewal automation and monitoring of expiry dates. This is ongoing effort, not a one-time task.
- Staff time: Initial deployment, JWT token authentication setup and upgrades fall to platform engineers. Ask whether an implementation partner will quote this as fixed scope.
Confirm with your team how many concurrent participants you expect at peak, because that number sets the bridge count and most of the recurring cost.
BigBlueButton is built for structured sessions with slides, whiteboard, polling, breakout rooms and recordings. The 4.0 server requirements are heavier and concentrated on one machine: at least 16 GB of RAM with swap, 8 CPU cores with high single-thread performance, 500 GB of disk for recordings (50 GB without recording) and 250 Mbit/s symmetrical bandwidth. Because a single session is resource-intensive, cost planning centers on how many simultaneous classes or webinars one server must carry, and on storage for recordings.
- Server sizing: Each BigBlueButton server is sized as a unit. Adding capacity usually means adding servers and a balancing layer such as Scalelite, which the project documents.
- Storage: Recording retention drives disk cost and backup scope. Decide the retention period before choosing disk size.
- Bandwidth: The 250 Mbit/s symmetrical requirement is a fixed baseline per server, so it recurs for every node you run.
- LMS and Greenlight: Embedding in Canvas, Moodle or other learning management systems, and running Greenlight rooms with OpenID Connect sign-in through Keycloak, add integration work to the implementation budget.
- Upgrades: Direct upgrades from 2.6, 2.7 or 3.0 to 4.0 are not supported, so a clean server installation is recommended. Budget a migration window rather than an in-place upgrade.
Before comparing totals, ask a provider to show the cost of a single BigBlueButton server at your target session count, including recording storage.
Questions buyers ask about Webex and self-hosted Jitsi costs
Can our own team deploy self-hosted Jitsi without outside help?
Often yes, if you already run Linux servers, DNS, TLS certificates and firewall rules well. The Jitsi self-hosting guide describes a web front end, the Prosody XMPP server, Jicofo and Jitsi Videobridge, and it is available as Docker containers or Debian and Ubuntu packages. The harder parts are usually not the install itself. They are a valid domain with a proper certificate, since Jitsi states HTTPS is necessary for multimedia to work, plus authentication, firewall ports for media, and load planning. Ask your team to map these against the Jitsi handbook before deciding whether to build in-house or hire help for a fixed scope.
How long does a self-hosted Jitsi deployment take?
No researched figure supports a firm duration, so treat any number you hear as unverified. Time depends on how many videobridges you run, whether you add JWT or LDAP sign-in, whether you connect SIP room systems through Jigasi, whether recording with Jibri is needed, and how many existing Webex workflows must be replaced. Ask any implementation partner for a written scope with milestones and deliverables before work starts, and confirm which of these items are included.
What skills does a self-hosted Jitsi team need?
You need people who can operate Linux, Docker or Debian packages, DNS, TLS certificates, reverse proxies and firewalls, and who can read network logs during a call. The Jitsi Docker setup runs separate web, prosody, jicofo, jvb, jigasi and jibri containers, so someone must understand container networking and configuration in the .env file. Identity work adds skills in JWT token authentication and, if you use directory sign-in, LDAP. Confirm these skills in your own team before costing the work, because they determine whether the cost is internal salary time or external fees.
What drives the implementation fee for a Jitsi migration?
The fee follows the written scope. The main drivers are the number of meeting rooms and users to set up, the authentication model, whether SIP room devices must be bridged through Jigasi, how many recordings must be archived, the number of videobridges and network design, and the security evidence you need for compliance reviews. DeployOpen does not publish a price list. A quote follows from a written scope that lists deliverables, responsibilities and exclusions, and most engagements are fixed-scope.
Does Jitsi Meet charge a license fee?
Jitsi Meet is licensed under Apache 2.0, so the software itself carries no license fee to download and self-host. Your costs come from the infrastructure, staff time and any outside support you buy. Jitsi is a trademark of 8x8, Inc., which also offers JaaS (Jitsi as a Service), a hosted option with its own commercial terms. If you choose JaaS instead of self-hosting, read its pricing and terms directly from the vendor, since they are outside this comparison. Also confirm your Webex contract terms, because licensing differences do not remove existing renewal obligations.
What does ongoing Jitsi operations involve after go-live?
Operations are recurring work, not a one-time event. Expect patching of the operating system and Jitsi releases (the project tags stable builds by number, such as stable/jitsi-meet_11248), monitoring of the central server and videobridges, certificate renewal, backup of configuration, and capacity checks before busy periods. The scalable setup guide says videobridges scale horizontally by adding more, so capacity planning becomes a recurring task. Decide whether your staff, a managed retainer or a mix will carry these tasks, and write the response times you need into the agreement.
What should we ask for in a quote for a Jitsi replacement?
Ask for a written scope that names every system, environment and integration, plus a list of deliverables, milestones and acceptance tests. Require a bill of materials for servers, bandwidth and storage, separated into one-time and recurring items. Ask who handles HTTPS certificates, authentication setup, backups, upgrades and incident response, and what is excluded. Request the assumptions behind any sizing, including the number of concurrent participants and the bandwidth per videobridge. Finally, ask how Webex contract overlap, data export and user training are priced, so you can compare the quote with your current Webex subscription and any Video Mesh costs on equal terms.
How do Webex subscriptions and Video Mesh costs compare with self-hosting?
Compare by component, not by one headline number. A Webex subscription is recurring and covers the cloud service, while Video Mesh nodes add on-premises server hardware, Cisco-side management in Control Hub and continuing dependence on the Webex cloud. A self-hosted Jitsi platform replaces the subscription with your own servers, bandwidth, staff time and any outside support, most of which is one-time setup followed by recurring operations. Confirm your current Webex licence counts, Video Mesh node requirements and renewal dates with your Cisco account team, then model each component over the same period.
What to ask for in a fixed-scope implementation quote
A written scope is what makes a self-hosted Jitsi quote comparable with the Webex run cost. DeployOpen agrees scope, deliverables and timelines in writing before work starts and does not publish a price list, so the quote follows from the document you approve. Ask for the components to be listed by name: the web front end, Prosody, Jicofo, the Jitsi Videobridge instances, and whether Jibri (recording and streaming) or Jigasi (SIP gateway) is in or out. Each optional component changes the server count and the operations load, so each should appear as an included item or an explicit exclusion.
Ask the scope to state the number of videobridges, the expected concurrent participants they are sized for, and the hardware or cloud instance profile per bridge. Jitsi's scalable setup guide describes horizontal scaling by adding bridges, so the scope should say how new bridges are added later and whether that work is priced separately. For authentication, name the method (internal XMPP accounts, JWT tokens, LDAP or Matrix verification, as the Docker guide lists) and confirm that HTTPS with a proper domain certificate is included, since self-signed certificates cause problems for mobile clients. Recording migration should specify what happens to existing Webex recordings, in which formats, and where they are stored.
The remaining items decide what you keep paying for after go-live. Ask for backup scope (what is backed up, retention, and a tested restore), the upgrade approach (how Jitsi releases are tested and applied, and whether upgrades are a retainer or an additional fixed-scope item), and handover documentation with a named set of runbooks. List exclusions explicitly, such as Webex device integration, SIP room systems, network firewall changes and user training. Confirm with DeployOpen and your own network team who owns the TURN or firewall work, because UDP media ports must be reachable from your users. Quotes that leave these lines blank are the ones that produce surprise costs later.
How DeployOpen scopes a fixed-price implementation
DeployOpen is a Chainscore Labs company that plans, implements, hardens, backs up and documents self-hosted open-source platforms inside your own infrastructure. For a Webex cost comparison, we start from a written scope that separates the subscription you would keep, the servers and bandwidth you would take on, and the staff time each option needs.
How we scope
- Inventory current Webex licenses, Video Mesh node counts and the meeting volume your teams actually use
- Agree which meeting types, room systems and recording needs move to Jitsi and which stay on Webex
- Document hardware, bandwidth and staff assumptions in the written scope before any work begins
- Engagements are fixed-scope, so scope, deliverables and timelines are agreed in writing first
How we build
- Size Jitsi web, Prosody, Jicofo and videobridge hosts against the concurrency figures from your inventory
- Configure HTTPS with a proper domain certificate, since Jitsi needs it for working audio and video
- Test audio, video and firewall paths from representative networks, including locations behind restrictive firewalls
- Model the recurring cost of servers, bandwidth and operations so the comparison uses your own numbers
How we hand over
- Deliver installation records, configuration, sizing worksheets and the cost model used in the comparison
- Write runbooks for upgrades, certificate renewal, scaling videobridges and restoring service
- Walk your operations staff through the platform so cost and ownership responsibilities are clear
- Confirm with your own environment and vendors which Webex features you still need before cutover
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Retainers can cover Jitsi release upgrades, backup checks and periodic capacity reviews
- Ask any provider to state in the quote which recurring tasks are included and which your team keeps
- Quotes follow from the written scope, and DeployOpen does not publish a price list
