BestVPSFor Editorial Team
Reviewed against the official Synapse documentation and current provider documentation linked below.
Published Jan 15, 2026 · Updated Oct 24, 2026
Matrix VPS Hosting 2026: Synapse Server Requirements
Plan a Matrix Synapse VPS with PostgreSQL, federation, TURN, backups, and realistic RAM and storage headroom, then compare four hosting options.
There is no official one-size-fits-all Matrix VPS minimum. A quiet private server, a public federated room, and a media-heavy community put very different pressure on Synapse, PostgreSQL, storage, and networking. Buy for the deployment you will operate, not for a headline price.
Compare deployment-fit VPS options ↓Short answer: start with headroom, then measure
The profiles below are conservative planning baselines from our editorial method. They are not official Synapse limits and they are not performance guarantees. The official documentation describes Synapse as memory hungry and recommends PostgreSQL for almost every installation, but it does not publish a universal RAM number.
| Deployment profile | Planning baseline | What changes the requirement |
|---|---|---|
| Private test server | 2 vCPU, 4 GB RAM, 40 GB SSD | A few users, limited federation, light media, no reliability promise |
| Small persistent team | 2 to 4 vCPU, 8 GB RAM, 80 GB SSD | PostgreSQL, active rooms, bridges, local uploads, monitoring, backups |
| Public or busy homeserver | 4 dedicated vCPU, 16 GB RAM, 160 GB SSD as a test starting point | Large federated rooms, many remote servers, calls, media retention, workers |
Do not size by local user count alone. Joining a large federated room can create more database, memory, network, and file-handle work than adding several users to small private rooms. Keep enough room to resize without rebuilding the server identity.
The six checks that decide whether a VPS fits Matrix
PostgreSQL, not SQLite
Synapse defaults can make a test easy, but the official installation guide says SQLite should not be used for production. Plan CPU, RAM, disk I/O, database updates, and database backups from day one.
Server name before the first user
The server name becomes part of every Matrix ID and room alias. Choose whether identities should use your root domain or a Matrix subdomain before creating the homeserver.
HTTPS and federation
Clients normally use TCP 443. Federation uses TCP 8448 by default, or 443 with correct delegation and reverse-proxy routing. The provider firewall and any external firewall must agree.
TURN for calls
Synapse is not the media relay for voice and video. Reliable calls need a separate TURN service with a public IP, TCP and UDP reachability, relay ports, and monitoring.
Media growth
Local uploads, avatars, thumbnails, and remote cache consume disk. Set upload and retention policy, watch the media store, and price attached storage before the root disk becomes the bottleneck.
Recoverable backups
A useful backup includes configuration, the signing key, PostgreSQL, and local media. Store a copy outside the VPS and test the restore procedure before treating the service as dependable.
Four VPS options, compared by deployment fit
We did not benchmark these providers for this page and we do not assign synthetic scores. The table uses current official product documentation and the Matrix operating checks above. Open the provider order screen to confirm the current region, term, IP, backup, storage, tax, and total.
| Provider | Useful when | Check before ordering | Current options |
|---|---|---|---|
| DigitalOcean | You want a conventional Linux VM, a documented resize path, and optional block storage. | Choose shared or dedicated CPU by sustained load. Include backups, volumes, transfer, and current per-second billing behavior. | View DigitalOcean Droplets → |
| Hetzner | You want shared or dedicated Cloud resources and your users fit an available European, US, or Singapore region. | Public IPs are separate resources, prices vary by network zone, and a powered-off server continues billing. | View Hetzner Cloud → |
| Hostinger | You prefer a fixed KVM bundle with RAM, NVMe storage, transfer, and weekly backup features in one plan. | Compare introductory and renewal terms. Hostinger documents CPU credits that can reduce available CPU after the balance is exhausted. | View Hostinger VPS → |
| Vultr | You value a broad region list, hourly capped billing, and a choice between shared and dedicated CPU products. | Plan availability and price vary by region. Backups, Block Storage, reserved IPs, and optional DDoS can add to the server bill. | View Vultr options → |
Railway is not included in this VPS shortlist because this guide is about operating a full homeserver on a general-purpose virtual machine with direct control over networking, storage, PostgreSQL, backups, and TURN.
Budget for the complete homeserver
Compute and database
Shared CPU can work for a private or lightly used server. Move toward dedicated CPU when database latency, federation queues, or sustained load matters more than the lowest entry price.
Primary and attached storage
PostgreSQL benefits from fast local storage. Media can grow independently and may justify an attached volume, but a volume does not replace a backup.
TURN traffic
Relayed calls can add network usage and may need a separate small instance. Include the public IP and UDP relay range in the architecture and cost.
Off-server backup
Provider snapshots are convenient but should not be the only recovery copy. Price database dumps, configuration, signing key, and local media in a separate failure domain.
A production-safe setup order
- Choose the permanent server name. Decide the Matrix identity domain before generating the Synapse configuration.
- Provision Linux and PostgreSQL. Use a supported Synapse installation path and a current PostgreSQL version supported by that Synapse release.
- Place Synapse behind HTTPS. Configure the reverse proxy, preserve the required request paths and headers, and keep the internal listener private.
- Configure federation. Use 8448 directly or delegate to 443, then validate the public server name and federation path.
- Add TURN if calls matter. Give the TURN endpoint a public IP, open the required TCP and UDP ports, and test from different networks.
- Create and restore a backup. Include the signing key, configuration, PostgreSQL, and local media. A successful backup job without a restore test is not a recovery plan.
- Measure before inviting more users. Watch memory, swap, database latency, disk growth, file handles, federation errors, and TURN traffic.
Common buying mistakes
A sound purchase
- Leaves RAM and disk headroom for federation and media.
- Uses PostgreSQL for a persistent deployment.
- Supports the required inbound and outbound ports.
- Can resize without changing the Matrix server name.
- Has an off-server restore path.
A fragile purchase
- Assumes two local users always mean a tiny workload.
- Uses SQLite because it is the quickest default.
- Ignores TURN until calls fail across networks.
- Prices only the root disk and not media growth.
- Treats a provider snapshot as the only backup.
Sources and checking method
Matrix facts were checked on October 24, 2026 against the official Synapse installation guide, PostgreSQL guide, reverse-proxy guide, federation guide, TURN guide, backup guide, security guide, and the official Docker documentation.
Provider facts were checked against official DigitalOcean Droplet documentation, Hetzner Cloud documentation, Hostinger VPS limits, and the Vultr Cloud Compute overview. Prices, regions, taxes, terms, and availability can change. Confirm the final order summary.
The three numeric deployment profiles are clearly labeled editorial planning baselines. They are intentionally not presented as official Synapse minimums or measured provider benchmarks.
Pick the provider only after the server name, database, federation path, TURN requirement, media policy, and restore plan are written down.
Frequently Asked Questions
How much RAM does a Matrix Synapse server need?
Synapse does not publish one universal RAM minimum because room size, federation, media, bridges, and user activity change the load. For planning, 4 GB is a cautious lab starting point and 8 GB gives a small persistent team more headroom. These are editorial starting points, not official guarantees. Monitor memory, database latency, disk growth, and federation queues before adding users.
Should a production Synapse server use PostgreSQL?
Yes. The official Synapse installation guide says almost all installations should use PostgreSQL and that SQLite is acceptable only for testing. Include the database, credentials, maintenance, and backups in the VPS plan.
Which ports does a Matrix homeserver need?
Clients normally reach Synapse over HTTPS on TCP 443. Federation uses TCP 8448 by default or TCP 443 when correctly delegated. Reliable voice and video calling also needs a TURN service with its own TCP and UDP ports and a public IP.
Can I change the Matrix server name later?
Treat the server name as permanent. It becomes part of user IDs, room aliases, and federation identity. The official installation guide says to choose it before installation because it cannot be changed later.
Does Matrix voice and video require TURN?
For reliable calls across different networks, yes. The official Synapse installation guide says a TURN server must be configured. The TURN endpoint needs a public IP and the documented relay ports.
What must a Matrix backup contain?
Back up the Synapse configuration, server signing key, PostgreSQL database, and local media store. The official backup guide explains that local uploads may be the only copy in the federation, so a database-only backup is incomplete.