Cisco Meeting Server cost vs self-hosted Jitsi

When the user base is stable and the renewal is the trigger, the comparison is mostly about recurring costs. On the Cisco side, the largest recurring lines are usually the Cisco support contract, the Smart Licensing entitlements for the PMP Plus and SMP Plus hosts, and the hardware or VMware subscription that keeps the Meeting Server nodes running. On the Jitsi side, the recurring costs are the servers, the bandwidth and the staff time to patch and monitor. Because load is flat, the server sizing can be fixed early, which makes the cost difference easier to see line by line.

• Licensing and support lines: Ask the vendor to itemize each Smart Licensing entitlement, each host and the support term, so you can see which lines end at renewal.
• Hardware or hypervisor lines: Separate the Meeting Server hardware refresh cost from the VMware host cost, since they age on different schedules.
• Meeting Management: Confirm whether the management licensing and support are priced separately from the call bridge hosts.
• Jitsi run costs: Estimate the central server and videobridge machines for your current peak, then add bandwidth and monitoring.
• Staff time: Count the hours your team already spends on Cisco upgrades and compare them with the patching and upgrade work your team would take on for Jitsi.

Before you sign a renewal, confirm the end date of every support term and the notice period so you do not commit to another cycle by default.

When meeting volume is rising, the cost question changes from licenses to capacity. A Jitsi deployment scales horizontally by adding videobridges, and the Jitsi scalable setup guide suggests 4 or 8 CPUs with 8 GB of RAM for each videobridge, with a 4 CPU, 8 GB machine for the central server. Cisco scales by adding call bridge hosts, each carrying its own licensing and support. Cost therefore grows in steps with each added node on both sides, so the quote should show the price of the next node, not just the current estimate.

• Videobridge count: Model cost per additional videobridge, including the CPU, memory and bandwidth it consumes at your peak.
• Bandwidth at peak: Ask who pays for the uplink and whether the peak is covered by an existing contract or an added one.
• Per-host licensing: On the Cisco side, ask what the next PMP Plus or SMP Plus host adds to the annual figure.
• Illustrative example: If peak concurrency doubles, a team might need twice the videobridge capacity but only one extra central server, so the marginal cost of Jitsi is mostly hardware and bandwidth.
• Load testing: Budget time for a load test before go-live, because the number of videobridges needed is not known until you measure your own meetings.

Ask the vendor to show the cost of each step up in capacity, and to state which parts of that cost are one-time and which recur.

When recording is required, the cost profile changes most. Jitsi recording runs through Jibri, an optional component that needs its own capacity, and the Jitsi Docker guide lists Jibri as a separate container. On the Cisco side, recording is typically tied to additional server capacity and storage. Storage is often the line that grows fastest, so the quote should separate compute for recording from long-term storage and retention.

• Jibri capacity: Recording consumes CPU and memory on a dedicated node, so count recording sessions that run at the same time, not total users.
• Storage for recordings: Price disk for retained recordings separately from disk for the operating system. BigBlueButton's install documentation pairs 500 GB of disk for recordings with a 16 GB memory and 8 CPU server, which is one reference point for sizing.
• Retention and export: Ask how recordings are exported, in which file formats and with which metadata, so the archive does not lock you in.
• Legal review: Recording may trigger notice or consent obligations, so budget time for your legal and compliance team.
• Quote request: Ask the vendor for the recording license terms, any per-recording or per-port charge, and what happens to recordings when a license lapses.

Confirm with your legal team which recordings must be kept and for how long before you size storage, because retention drives the largest recurring line.

When the network is regulated and must host its own servers, the largest cost lines are often the ones that do not appear on a vendor price list: the hardening, the evidence collection and the offline operations. Cisco Meeting Server depends on Smart Licensing and Meeting Management registration, which need a path to the license infrastructure. Jitsi needs no license server, but it does need HTTPS with a proper domain certificate, since the Jitsi handbook says self-signed certificates cause problems. Each approach moves some work onto your team and some onto the vendor.

• Licensing in isolation: Ask how Smart Licensing reporting works on a disconnected network and who handles the offline steps.
• Certificates and identity: Budget for a certificate authority, and for an authentication design that uses JWT tokens or an approved identity provider.
• Hardening and testing: Count the time to harden the servers, test them and document the controls an assessor will ask about.
• Update path: Ask how security patches reach each system on a closed network, and who is responsible for applying them.
• Support scope: Confirm whether the vendor or your implementation partner will support the system on your network, and under what written terms.

Before you request a quote, confirm the accreditation boundary and the approved update process with your security team, since both decide how much of the cost is one-time and how much recurs.