CryptoServers

Matrix homeserver hosting on offshore hardware

Synapse, Dendrite or Conduit on hardware sized for federation — your homeserver, your room IDs, your retention policy.

No KYC, ever DMCA ignored No traffic logs Live in 60 seconds
1 Tbps
DDoS absorption
41s
Median deploy
3
Recommended locations
$39.99
Entry plan / month
Built for the workload

Why Matrix homeserver hosting runs better here

Specific technical alignment, not generic copy. Each point below is something the workload needs and we provide by default.

Federation port 8448 open. Stable IP for federated room consistency.
NVMe Postgres path. Synapse media + db + workers fit cleanly on Business and up.
Worker-pattern Synapse runs comfortably on Pro; CLN/LND-style 4-worker layouts on Bastion.
No filtering of federated traffic. End-to-end encryption fully intact (we never see message bodies).
No retention beyond 24 hours of operational logs. Federation graphs not stored.
Workload notes

What you should know about Matrix homeserver hosting on Cryptoservers

A Matrix homeserver gets heavier as the federated room set grows — Synapse's Postgres database can outgrow a 60 GB disk in a year of active federation with 50 active users. Sized to vps-business at 240 GB NVMe minimum; for a public homeserver expect to outgrow that into ded-shield within 12–18 months. The CPU profile is bursty (encryption key shuffling), not sustained.

Federation requires inbound 8448 (or your TLS-terminated variant) with stable IPv4 — same constraint as a Lightning node. We don't filter Matrix federation traffic, don't cap connection count, and don't fingerprint Synapse's worker pattern. Multi-worker Synapse setups (master + 3 workers) run fine on vps-pro; for performance-critical public homeservers, ded-shield with 2× NVMe lets you split Postgres onto its own disk.

Sysadmin FAQ

Matrix homeserver hosting — questions answered

Synapse, Dendrite or Conduit?
Synapse is the reference (Python, batteries-included, heaviest). Dendrite is the Go rewrite (lighter, more modern, less mature). Conduit is the Rust minimalist for small homeservers. For 1–10 users: Conduit. For 10–500: Dendrite or Synapse. For public/federated: still Synapse.
How much disk does a year of federation consume?
For a homeserver with 20 users in 200 federated rooms: ~30–80 GB after a year (Postgres + media). Public homeservers in popular rooms can hit 200 GB in 6 months. Plan for outgrowing the smaller VPS tiers within 12 months if you're running federation hot.
Can I run a Matrix bridge to IRC or Telegram on the same box?
Yes — bridges are userland processes (matrix-appservice-irc, mautrix-telegram, etc.) and add minimal load. The IRC bridge can be chatty on memory if you join hundreds of channels; size accordingly.
What about your chosen jurisdiction specifically — any local data-residency rules I should know?
Iceland and Switzerland are outside EU GDPR jurisdiction (Iceland is EEA but with lighter enforcement). Netherlands and Romania are EU — GDPR applies, but there are no Matrix-specific obligations beyond standard data-controller hygiene. Pick by user latency, not legal exposure.
Do you backup the Postgres for me?
No managed backup layer. Snapshots happen hourly with 7-day retention (panel-level, not Postgres-aware). For point-in-time DB recovery, run pg_basebackup + WAL archiving on your own box or to a second cryptoservers VPS in a different jurisdiction.

Matrix homeserver hosting — deploy in 60 seconds

No email, no ID, no account. Pick a plan, pay in crypto, get root.