keepcalculator

06 Numbers and Powers

Jitsi Meet VPS: What to Know Before Buying

Card No. 06·71825 · Updated · Standard formula, shown below

Before buying a virtual dedicated server (VPS) for Jitsi Meet, you need to know that the hardware specs alone won’t guarantee good call quality—you must also configure the server for WebRTC, plan for bandwidth, and understand that Jitsi’s performance depends heavily on the number of simultaneous participants and whether you enable recording or live streaming. This article explains the key factors to evaluate: CPU, RAM, network, storage, software setup, and ongoing maintenance, so you can choose a VPS that actually works for your use case.

Background: What Jitsi Meet Is and Why It Needs a Server

Jitsi Meet is an open-source video conferencing application that runs in a browser without requiring users to install anything. It uses WebRTC (Web Real-Time Communication) to send audio and video directly between participants, but a central server is still needed for signaling, managing rooms, and—in many cases—relaying media when direct peer-to-peer connections fail. When you self-host Jitsi on a VPS, you control the server, your data, and the configuration, which is why many privacy-conscious organizations choose it over hosted services like Zoom or Google Meet.

However, self-hosting means you are responsible for the entire stack: the operating system, the Jitsi Meet web interface, the videobridge (a component called Jicofo and another called JVB), and often a TURN server for NAT traversal. A VPS gives you dedicated resources (CPU, RAM, disk) that are not shared with other customers, unlike shared hosting. But “dedicated” in the VPS context means the resources are reserved for you, not that you get a physical machine to yourself—that would be a dedicated server, which is more expensive.

How Jitsi Meet Uses Server Resources

Jitsi Meet’s architecture matters when choosing a VPS. The main components are:

  • Web server (Nginx): Serves the static files and handles HTTPS. Light on CPU.
  • Prosody (XMPP server): Handles signaling, presence, and room management. Low to moderate CPU and RAM.
  • Jicofo: The conference focus component that manages sessions. Moderate CPU.
  • Jitsi Videobridge (JVB): The media router that forwards video and audio streams. This is the resource hog—it uses CPU for packet processing and bandwidth for every participant’s streams.
  • Optional components: Jigasi (SIP gateway), recording (Jibri), and live streaming also consume significant CPU and RAM.

In a typical conference, each participant sends their video to the JVB, which then forwards it to all other participants (in a mesh topology) or uses selective forwarding (SFU) to send only the streams each participant needs. The JVB does not transcode video (that would be much heavier), but it does do packet routing, which still requires CPU and network throughput.

Choosing the Right VPS Specs

The specs you need depend on the maximum number of concurrent participants and whether you plan to use features like recording. As a rule of thumb:

  • CPU: Jitsi is CPU-bound, especially with many participants. For up to 10 participants, 2 vCPUs is sufficient; for 20-30, go with 4 vCPUs; for 50+, consider 8 vCPUs or more. Modern CPUs with high single-thread performance are better.
  • RAM: The base installation uses about 1-2 GB. Each participant adds roughly 50-100 MB of RAM for the JVB, so for 20 participants, 4 GB is a safe minimum. For 50, 8 GB is better.
  • Disk: The OS and Jitsi software take about 5 GB. If you record meetings, you’ll need much more—an hour of HD video can be 1-2 GB, so plan accordingly.
  • Bandwidth: This is often the bottleneck. Each participant in a video call uses about 1-2 Mbps for video and 100-200 kbps for audio. With 10 participants, you need at least 20 Mbps upload and download on the server. For 50, you need 100 Mbps or more. Check the VPS provider’s bandwidth limits and whether they charge for overage.

Also consider that a VPS with a burstable CPU (like some providers offer) may throttle performance under sustained load, which can cause jitter and dropped frames during long meetings. Look for “guaranteed” or “dedicated” vCPU allocations if possible.

Network and Latency Considerations

Jitsi Meet is latency-sensitive. A server in a different region from your users will add delay, which degrades the experience. Choose a VPS provider with data centers close to your primary user base. Also, ensure the provider has a good upstream network and doesn’t throttle UDP traffic, since WebRTC uses UDP for media.

You’ll also need to open specific ports on the firewall: TCP 80/443 for HTTPS and UDP 10000 for the videobridge. If you plan to use TURN (for users behind strict NATs), you’ll need additional ports (typically UDP 3478 and a range like 49152-65535). Some providers block certain ports or have DDoS protection that can interfere with UDP traffic—check their policies.

Common Problems and How to Avoid Them

Many first-time self-hosters run into the same issues:

  • No audio/video after setup: Usually a firewall or NAT issue. Ensure UDP 10000 is open and that your server has a public IP (no carrier-grade NAT).
  • Poor quality with many participants: Often due to insufficient bandwidth or CPU. Use the Jitsi statistics page (accessible via a special URL) to monitor packet loss and CPU usage.
  • SSL certificate errors: Jitsi uses Let’s Encrypt for free SSL, but you must have a domain name pointing to your server. Using an IP address only will cause certificate warnings.
  • Recording fails: Jibri requires a virtual display and Chromium; it’s resource-intensive and often fails on low-spec VPS. Consider using a separate server for recording if you need it.

To avoid these, follow the official quickstart guide, which uses a script that automates most of the setup. But know that the script assumes a clean Ubuntu server with a domain name and open ports.

Costs and Alternatives

VPS pricing varies widely. A basic 2 vCPU/4 GB VPS with 1 TB bandwidth might cost around $20-40 per month, while a 4 vCPU/8 GB with 2 TB might be $40-80. You also need a domain name (~$10/year) and possibly a TURN server if you have many users behind strict firewalls. Compare this to using a hosted Jitsi provider (like meet.jit.si) which is free but has no guarantees, or a paid service like Zoom which charges per host.

If you’re not ready for the maintenance, consider using a managed Jitsi hosting service or a turnkey appliance. However, if you need full control and data privacy, a VPS is the way to go.

Security and Maintenance

Self-hosting Jitsi means you’re responsible for security updates. The Jitsi team releases updates regularly, and you should apply them. Also, by default, Jitsi Meet rooms are open—anyone with the link can join. You can enable authentication (using a password or a secure room name) and use the built-in lobby feature. For sensitive meetings, consider using end-to-end encryption, which Jitsi supports but with limitations (no recording, no live streaming, and no server-side features).

Backup your configuration files, and monitor server logs for suspicious activity. Use a firewall and fail2ban to protect against brute-force attacks on SSH.

Frequently Asked Questions

How many participants can a 4 vCPU/8 GB VPS handle?

On a 4 vCPU/8 GB VPS with good bandwidth, you can typically support 20-30 participants in a video call, assuming moderate resolution (720p) and no recording. The exact number depends on the CPU model and network quality. If you need more, you can scale out by adding more JVB instances, but that’s advanced.

Do I need a TURN server?

Not always. TURN is only needed when participants are behind symmetric NATs or strict corporate firewalls that block UDP. If your users are on home networks, they can often connect directly. However, if you have users in offices with strict firewalls, a TURN server (which relays traffic over TCP/443) can improve connectivity. Many VPS providers offer TURN as part of the setup.

Can I use Jitsi Meet on a VPS with an IP address instead of a domain?

Technically yes, but the default setup uses Let’s Encrypt, which requires a domain name. You can configure a self-signed certificate, but browsers will show warnings, and some WebRTC features (like screen sharing) may not work on insecure origins. It’s strongly recommended to use a domain.

What is the difference between a VPS and a dedicated server for Jitsi?

A VPS shares the physical hardware with other tenants, but you have dedicated vCPU cores and RAM. A dedicated server gives you the entire physical machine. For Jitsi, a VPS is usually sufficient unless you have hundreds of concurrent users. Dedicated servers are more expensive and require more management.

How do I know if my VPS bandwidth is enough?

Estimate your peak bandwidth by multiplying the number of participants by 1.5 Mbps (for video) plus 0.2 Mbps (for audio). For 20 participants, that’s about 34 Mbps. Check your VPS plan’s bandwidth limit (monthly transfer) and the network speed (e.g., 1 Gbps). Also, run a speed test from the server to a user’s location to see real-world throughput.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →