# Jitsi scaling and performance service

> We find your Jitsi server's real limits with load tests, then scale it: more videobridges behind one signalling server, regional bridges near your users, autoscaling that adds and drains bridges safely, and monitoring that shows bandwidth, CPU and call quality. You get a capacity report and a system that grows with demand.

Source: https://jitsi.help/services/jitsi-scaling/
Updated: September 26, 2026
Publisher: Jitsi Help (https://jitsi.help/)

Scaling Jitsi is less about bigger machines and more about the right architecture: one signalling layer, many videobridges, and an honest measure of what each one can carry.

## Our approach

1. **Review.** We look for the configuration problems that masquerade as capacity problems.
2. **Measure.** Load tests with realistic meetings, reported as participants and meetings per bridge.
3. **Scale out.** Extra bridges, regional placement, and autoscaling that drains a bridge before removing it.
4. **Observe.** Dashboards and alerts for bandwidth, CPU and quality.

The concepts are covered in our [scaling guide](/guides/jitsi-scaling-videobridge/).

## Get started

[Tell us](/contact/?topic=jitsi-scaling) your current setup, your peak usage and your target, and we will reply with a plan and a quote.

## Frequently asked questions

### How do we know we need to scale?

Choppy video or dropped participants at peak times, bandwidth near your server's limit, or plans to host much bigger meetings. We start with a review, because many of these are configuration problems that do not need more servers.

### Do you use Kubernetes?

Only if you already run it. For most teams, videobridges on plain virtual machines in an autoscaling group are simpler and more reliable for UDP media.


---

Jitsi Help is an independent service. It is not affiliated with, endorsed by or sponsored by 8x8, Inc. or the Jitsi project. Jitsi and Jitsi Meet are trademarks of 8x8, Inc., used here only to describe the software we host and support.