Installation

Choose the deployment path that matches how you operate the platform.

Scenario	Recommendation	Why
one VPS or staging environment	Docker Compose	fewer components to operate
distributed cluster	Docker Swarm	placement, overlay and service-level updates
no Docker runtime	Native Linux	immutable releases, systemd and rollback
telephony directly on the host	Native Linux telephony	predictable SIP and media ports

For a first installation, start with Docker Compose. As soon as HTTPS and the API are healthy, follow the quickstart; you do not need to read every deployment guide before testing a text message.

Choose the deployment model that matches your infrastructure. The unified container image can run the API, broker, Zapo worker, dedicated video worker and telephony process. Native Linux packages are also available.

Deployment options

• Docker Compose: one host, bridge networking and host networking for telephony.
• Docker Swarm: clustered services, overlay networks and explicit host-mode media ports.
• Native Linux installer: versioned releases managed by systemd.
• Native Linux telephony: SIP, RTP and WebRTC directly on the host while the API may remain in Docker.

Recommended minimum

Resource	Recommendation
CPU	2 cores
Memory	4 GB while building locally
State database	Valkey 9 or a compatible Redis server
Queue	RabbitMQ 4
HTTP port	9876

Do not publish Valkey or RabbitMQ to the internet. Terminate TLS at your edge proxy and use strong, unique tokens for every installation.