Jitsi service

Jitsi Hosting on AWS, Azure and GCP

We set up Jitsi Meet in your own cloud account and hand it over working: SSL, recording, a TURN server for strict firewalls, and videobridges that scale with your calls. You own every server.

  • Runs in your own AWS, Azure or GCP account
  • Jibri recording, TURN and SSO set up and tested
  • Auto scaling videobridges for busy hours
Jitsi Meet hosting on AWS, Azure and GCP

Jitsi Meet hosting in your own cloud account

Installing Jitsi is well documented. Getting it to work for everyone is not. The install finishes, you join a test call from your laptop, it works. Then someone joins from a hotel network and sees a black screen, because UDP 10000 is blocked and there is no TURN server to fall back on.

That gap between "installed" and "production" is what we do. A typical Jitsi server hosting setup from us includes:

  • Jitsi Meet, Prosody, Jicofo and one or more videobridges (JVB), sized for your peak call
  • Your domain with an auto-renewing SSL certificate
  • Jibri recording and live streaming, saving to your own S3 or Cloud Storage bucket
  • A Coturn TURN server on TCP 443 for users behind corporate firewalls
  • Secure rooms with JWT or SSO, so strangers cannot open meetings on your server
  • Monitoring, and a handover document your team can actually follow

Jitsi on AWS

Our Jitsi Meet images on AWS Marketplace launch through a CloudFormation stack into your account, sized for 50, 100, 250 or 500 concurrent users, with or without recording. If you only need a standard server, start from the store listing and skip the service entirely.

For bigger or custom setups we use our Jitsi Terraform scripts for AWS, which go up to multi-shard, auto scaling clusters for 2,000 concurrent users. One thing to plan for on new AWS accounts: the default vCPU quota is often too low for a cluster, and the quota increase can take a day or two to approve.

Jitsi on Google Cloud (GCP)

The same plans exist as Google Cloud Marketplace images, deployed into your own GCP project, with recordings going to a Cloud Storage bucket. The GCP plan comparison shows how many servers each plan runs. If your firewall rules target a network tag, a new videobridge without that tag joins the pool and then carries no media. We check that as part of every setup.

Jitsi on Microsoft Azure

There is no Meetrix marketplace image on Azure, so an Azure setup is a manual install with the official Debian packages or docker-jitsi-meet. It works well. It just takes longer than AWS or GCP. Open UDP 10000 and TCP 443 in the network security group, and use Virtual Machine Scale Sets if the videobridges need to scale.

Jitsi cloud sizing: which setup fits

Peak participantsSetupScaling
Up to 100One server running Meet and the videobridgeFixed size
250Meet server plus two videobridgesFixed size
500Meet server plus two or more videobridgesAuto scaling videobridges
1,000 to 2,000Several shards behind HAProxyAuto scaling, Octo across bridges

Add a Jibri server for each recording that runs at the same time. Jibri records one meeting per instance, which surprises almost everyone. The Jitsi architecture overview explains why.

Jitsi meet auto scaling on AWS, GCP and Azure

Auto scaling is worth it once your usage has peaks, like classes at 9am or a weekly all-hands. Scaling down matters as much as scaling up: a videobridge that stops while it still hosts a conference drops that call mid-sentence, so the scale-in rules need as much care as the scale-out ones.

Jitsi installation yourself, or with us

Honest answer: if you need one server for your own team, install it yourself. The Jitsi self-hosting guide is good, and our marketplace images make it faster still. Bring us in when you need recording, scale, SSO, a custom front end, or someone to call when it breaks. Our Jitsi support covers that last part, and we also do Jitsi customization and rebranding.

Frequently asked questions

How much does Jitsi hosting cost?

Jitsi Meet itself is free. You pay for the servers, bandwidth and whoever runs them. A 50-user server costs far less than a 500-user cluster with recording. Our self-hosting cost breakdown has real monthly numbers.

Can Jitsi Meet auto scale on AWS, GCP and Azure?

Yes. Videobridges and Jibri recorders scale out behind one signalling server on all three. AWS uses Auto Scaling groups, GCP managed instance groups, and Azure Virtual Machine Scale Sets. We have ready Terraform scripts for AWS.

How long does a Jitsi installation take?

A single server from our marketplace image is mostly a wait for DNS and the SSL certificate. A production cluster with recording, TURN, SSO and auto scaling takes longer, and most of that time is testing. We give you a timeline after scoping.

Which cloud is best for hosting Jitsi?

The one you already use. Jitsi runs the same on all three. AWS and GCP have our one-click marketplace images, which makes them fastest to start. Watch egress pricing, because video bandwidth is most of the bill.

Do you host Jitsi on your servers or ours?

Yours. Every server runs in your own cloud account, so recordings, logs and meeting data never leave it. We need temporary access to set it up, and you can revoke it after handover.