Matrix Synapse
Compare VPS plans to self-host Matrix Synapse. providers advertising 1GB+ RAM from $2/mo. Matrix Synapse server hosting comparison.
Find the best and cheapest VPS plans to self-host Matrix Synapse.
Minimum Requirements
These VPS plans meet the minimum requirements to run Matrix Synapse. Suitable for testing or light usage.
Recommended Requirements
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
Source: self-hosted-tools.json
Matrix Synapse VPS Sizing: Storage, Sync, and Scale
Matrix Synapse is the reference homeserver for a federated messaging network, not just a closed-team chat app. The hosting choice matters because the server has to process local users, media, encryption, and federation traffic at the same time while keeping room state consistent across many remote homeservers.
Resource Profile Classification
The primary resource profile is Memory-bound. self-hosted-tools.json starts Synapse at 1 GB RAM and recommends 4 GB, and that production jump is justified quickly once rooms become active. The biggest reason is federation overhead: Synapse keeps room state, membership graphs, event timelines, retry queues, and encryption-related metadata in motion for both local traffic and remote servers. That federation-memory-overhead is why 1 GB can boot a tiny private instance but feels cramped for a real community.
Federation makes Synapse heavier than a private chat server because room state, event history, key exchange, and remote-server retries all stay resident longer.
Storage and Network Interpretation
Treat Synapse as a database-backed communication system with high write churn. PostgreSQL is the production baseline, while SQLite is only suitable for very small testing. SSD or NVMe storage matters because room state writes, media records, and background jobs punish slow disks. Network quality also matters because federation depends on consistent inbound and outbound connectivity, but the first production bottleneck is often memory consumed by room state and federation queues rather than raw bandwidth. If provider uplink details are not documented locally, We recommend verifying the latest uplink specs directly on the provider's SLA due to regional variation.
Minimum vs Production vs Scale
| Stage | Source | CPU | RAM | Storage | Interpretation |
|---|---|---|---|---|---|
| Minimum | requirements.minimum |
1 Core | 1 GB | 20 GB | The 1 GB and 1-core floor is enough for installation or a tiny personal homeserver with minimal room state. It is not a durable public-community baseline. |
| Production | requirements.recommended |
2 Cores | 4 GB | 50 GB | The 4 GB and 2-core production tier is the starting point for a small live Synapse deployment using PostgreSQL, with room state, federation, and media all active. |
| Scale | editorial interpretation |
Add steadier CPU for event processing, media thumbnails, encryption-related work, and worker processes as communities grow. | Add RAM first for room state, federation queues, caches, and PostgreSQL working set because memory pressure is the first failure mode on undersized Synapse hosts. | Keep PostgreSQL and media metadata on SSD or NVMe and separate long-term media retention from the root disk as the homeserver grows. | At scale, Synapse growth is defined by federation overhead and room state complexity more than by the login page. The next move is more RAM, cleaner PostgreSQL performance, and worker isolation so federation traffic stops competing with local users for the same memory pool. |
Anti-Patterns
- Do not present Matrix Synapse as a simple private chat server if federation is enabled; federation overhead changes the memory and database story immediately.
- Do not treat the 1 GB minimum as a community-ready spec when room state, event history, and remote-server retries start to accumulate.
- Do not run production Synapse on SQLite and expect room state resolution to stay healthy under load.
- Do not ignore media growth, PostgreSQL care, and federation queues when judging a cheap first-term VPS offer.
Who It Fits
For: Good fit for operators who want a federated Matrix homeserver, accept PostgreSQL as the production baseline, and can budget for 4 GB RAM or more once rooms, users, and federation partners become active.
Not for: Avoid an entry-level VPS if you expect many rooms, active federation, public communities, heavy media use, or no operational budget for PostgreSQL and background-job tuning.
FAQ
Why does federation make Synapse so heavy?
Because federation forces the homeserver to track remote room state, event history, membership changes, retries, and key exchange alongside local traffic. That memory and database overhead grows faster than a closed chat server.
Is 1 GB RAM enough for Matrix Synapse?
Only for a tiny private instance or evaluation. The production baseline in self-hosted-tools.json is 4 GB RAM, and federation is the reason that jump matters.
What should I check before buying?
Check enough RAM for room state and federation queues, PostgreSQL-friendly SSD storage, media retention planning, renewal pricing, and network consistency for inbound and outbound federation traffic.
Quality Checks
- Engineering-Check: Yes, the page names the first bottleneck and its failure mode.
- Trade-off-Check: Yes, it states who should avoid an entry-level VPS.
- Renewal-Price-Check: Yes, buyers are warned that low first-term prices can distort VPS selection.
- Keyword-Anchor-Check: Yes, internal anchors on the page use VPS and self-hosting terms instead of generic labels.
- Data-Link-Check: Yes, Minimum and Production values map to
self-hosted-tools.json. - Uniqueness-Check: Yes, the analysis is tied to Matrix Synapse bottlenecks rather than a name-swap template.
What is Matrix Synapse?
Matrix Synapse is the reference homeserver implementation for the Matrix decentralized communication protocol. It enables secure, end-to-end encrypted messaging, voice and video calls, and federation with other Matrix servers. Users can communicate across different servers, creating a truly decentralized network. Matrix powers Element (formerly Riot) and is adopted by governments and enterprises for secure communication. Self-hosting gives you complete control over your communication data, but federation makes Synapse much heavier than a closed team chat server.
Why Server Specs Matter
Synapse is known for its high resource usage, primarily due to its Python implementation and the complexity of federation. The server maintains room state, handles encryption key distribution, stores message history, and processes federation traffic from other servers. Federation overhead is not just network traffic: it also creates memory pressure because room state, retry queues, membership changes, and event history stay active for both local and remote users. RAM usage scales significantly with the number of rooms, users, and federated servers. CPU is used for message processing and media thumbnail generation, while database size grows quickly with active rooms.
Problems with Undersized Servers
Insufficient resources cause severe problems with Synapse. Messages are delayed or fail to send, and federation with other servers times out, causing rooms to desync. The server becomes unresponsive during room state resolution, which is one of the clearest signs that federation-memory-overhead has exceeded the VPS headroom. Media uploads fail, login and registration time out, and background tasks pile up indefinitely. In extreme cases, the entire server crashes and requires database repair.
Our Recommendation
For personal use with only a few rooms, 1GB RAM can boot Synapse but usually feels constrained. Small communities should treat 2-4GB RAM as the realistic starting point, and active servers with many users, rooms, or federated peers often need 4-8GB or more. PostgreSQL is required for production because SQLite cannot handle the write pattern. Plan 20-50GB storage for media and the database, keep it on SSD, and expect federation overhead to be the main reason you outgrow an entry-level VPS.
Minimum Requirements - VPS Plans
These VPS plans meet the minimum requirements to run Matrix Synapse. Suitable for testing or light usage.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Recommended Requirements - VPS Plans
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Some links on this page are affiliate links. If you make a purchase through these links, we may earn a small commission at no extra cost to you. This helps us keep the site running and provide free comparison tools.