What you get
- Server sizing for your expected meetings and budget
- Jitsi Meet on Docker, pinned to a tested stable release
- Your domain with a trusted, auto-renewing SSL certificate
- Firewall and cloud security rules, SSH locked down
- Host login (secure domain) or JWT, lobby defaults
- Three-device call test on different networks
- Handover notes: where everything lives and how to upgrade
Typical timeline
1 to 2 working days
A Jitsi server that works in a two-person test and fails in a real meeting is the most common thing we are hired to fix. Our installation service gets it right the first time.
What we do
- Scoping call. How many people, how many rooms at once, recording or transcription, who should be allowed to host, where your users are.
- Sizing. We pick the server size and region, and show you the monthly infrastructure cost before anything is created.
- Install. Docker, pinned to a tested stable release, your domain, SSL, firewall, and the authentication model you need.
- Test. Three devices on different networks, screen sharing, host login, and your browsers.
- Handover. Admin access and plain-language notes: where the config lives, how to add hosts, how to upgrade.
Who it is for
- Companies that want private meetings on their own infrastructure.
- Schools, clinics and NGOs with data residency or privacy requirements.
- Developers who need a reliable Jitsi backend for their product.
Prefer to do it yourself?
The same recipe is in our Docker install guide, and on AWS our one-click platform does it automatically. The service is for when you want an engineer to own the outcome.