Voxport self-hosted communication server on open source Jitsi

Voxport is a self-hosted platform for voice and video communication. The default model: the server owner deploys a communication server on their VPS or hardware. That server is built on open source Jitsi Meet — an Apache 2.0 licensed project.

Voice and video do not pass through the Voxport platform. Media streams go through a Jitsi instance controlled by the server owner.

Creating a server · Central platform

Two-part architecture

Part	What it does	Where it runs
Voxport platform	Accounts, community servers, rooms, roles, invites, push, call metadata	Voxport infrastructure (voxport.net)
Communication server (Jitsi)	Voice and video over WebRTC	VPS or hardware owned by the server owner

The platform coordinates who is in which room. Jitsi carries audio and video between participants.

Jitsi stack in Voxport

For self-hosted deployments, Voxport uses a minimal Jitsi Meet stack via Docker Compose:

Component	Image	Purpose
web	jitsi/web	Jitsi web interface
prosody	jitsi/prosody	XMPP server (signaling)
jicofo	jitsi/jicofo	Conference focus (session management)
jvb	jitsi/jvb	Videobridge (media routing)

TLS terminates on host nginx. Authorization uses JWT — tokens issued by the Voxport backend.

E2EE (end-to-end encryption) is enabled by default.

Not included in the minimal stack

Optional upstream Jitsi services are not included:

• Jibri (recording)
• Jigasi (SIP/telephony)
• Etherpad
• Coturn
• Whiteboard

Recording, live streaming, and in-call chat are disabled in Voxport's configuration.

Installation with voxman

Step-by-step setup with app commands — see Creating a server.

voxman is Voxport's CLI tool that deploys Jitsi on your VPS automatically. You don't need to buy a domain, configure DNS, issue certificates, or assemble Docker containers manually.

What you need to do

1. A VPS running Debian 13+ (Ubuntu — later)
2. Connect via SSH once and run a few commands
3. voxman handles everything else

How it works

1. In the Voxport desktop app, create a server and choose self-hosted
2. The app shows two commands — install voxman and register with a one-time token
3. Connect to your VPS via SSH and run the commands
4. voxman registers the server, deploys Jitsi, and reports ready status to the platform
5. In the app, the server moves to "ready" — you can create rooms

Commands

Step 1 — install voxman:

curl -fsSL https://packages.voxport.net/debian/gpg | sudo gpg --dearmor -o /usr/share/keyrings/voxport.gpg
echo "deb [signed-by=/usr/share/keyrings/voxport.gpg] https://packages.voxport.net/debian stable main" | \
  sudo tee /etc/apt/sources.list.d/voxport.list
sudo apt update
sudo apt install -y voxman

Step 2 — register your VPS and deploy Jitsi (token and URL are shown in the app when creating a server):

sudo voxman setup --token <your-token> --api https://voxport.net

One setup command runs the full cycle:

• registers your VPS on the Voxport platform with a one-time token
• assigns a domain to the server (e.g. my-server.host.voxport.cloud)
• configures DNS — the record points to your VPS public IP
• issues a TLS certificate (Let's Encrypt) and sets up HTTPS
• installs Docker and deploys Jitsi containers
• configures nginx (reverse proxy) and firewall (UFW)
• JWT authorization — links Jitsi to the Voxport platform

When finished, Jitsi is available at https://<your-domain>. Media streams go through your VPS.

Management after installation

Command	Action
voxman status	Component status
voxman doctor	Diagnostics
voxman update jitsi	Update Jitsi containers
voxman backup / voxman restore	Configuration backup
voxman jitsi e2ee	E2EE status

Manual deployment without voxman

voxman is not required. It's the recommended way for a quick install, but if needed you can deploy the entire infrastructure yourself — on your own domain, your own VPS, with full control over configuration.

Self-hosted in Voxport means Jitsi runs on your infrastructure. How you install it — via voxman or manually — is up to you.

What to do manually

1. Deploy Jitsi Meet on your server — official Docker images or any method from the Jitsi handbook
2. Configure your domain, DNS, and HTTPS (TLS certificate)
3. Enable JWT authorization on Jitsi — Voxport clients connect only with a token issued by the platform
4. Set parameters in server settings in the Voxport app:
   • communication server domain
   • JWT secret and issuer (shared secrets between Jitsi and the Voxport platform)

After that, the Voxport platform coordinates rooms and issues JWTs, while media still flows through your Jitsi — no voxman needed.

voxman vs manual installation

	voxman	Manual installation
Domain	Assigned automatically	Your own
DNS and HTTPS	Configured automatically	You configure yourself
Jitsi	Deployed with one command	You install yourself
JWT link to Voxport	Configured automatically	You configure yourself
Control	Standard Voxport configuration	Full configuration freedom

Both options deploy Jitsi on your VPS — media does not pass through the Voxport platform.

How a call works

1. A participant opens a room in the Voxport client
2. The Voxport platform checks permissions and issues a JWT for Jitsi
3. The client connects to Jitsi on the owner's VPS over WebRTC
4. Voice and video go directly through Jitsi Videobridge — not through the Voxport backend

Self-hosted vs Voxport Cloud

	Self-hosted	Voxport Cloud
Who deploys Jitsi	Server owner (voxman or manually)	Voxport
Where media flows	Owner's VPS/hardware	Voxport VPS
Technology	Open source Jitsi Meet	Open source Jitsi Meet
Voxport platform	Yes	Yes

In both cases, media is carried over Jitsi/WebRTC. The difference is who owns and administers the communication server.

What Voxport does not control with self-hosted

• voice and video media streams
• the owner's VPS infrastructure
• conversation content

Voxport only controls the management platform: accounts, rooms, metadata, coordination.