CryptoServers
Launch server

Tor relay & exit hosting on offshore hardware

Tor relays, bridges and exits on a network that publishes its abuse posture and won't pull the plug after one boilerplate notice.

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

Why Tor relay & exit hosting runs better here

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

Tor exits are allowed, not just tolerated. Relays included by default in our anycast scrubbing fabric.
1 Tbps DDoS absorption — exits draw the traffic that VPNs draw, plus reflection probes.
IPv4 + /64 IPv6 on every plan. Ed25519 SSH keys; no password auth on our side.
48-hour abuse response window. CSAM and credible-threat content excepted (acted on within 4 hours).
No bandwidth re-billing on overage — you stay on the plan you ordered.
Workload notes

What you should know about Tor relay & exit hosting on Cryptoservers

Cryptoservers explicitly allows Tor relays, including exit nodes. We respond to legitimate abuse (CSAM, credible threats, phishing) within 48 hours; everything else stays up. Each location publishes its peering and the upstream carriers it announces under our ASN, so you can pick a relay home that won't disappear behind a forwarded DMCA email.

For relays you'll typically size to vps-growth or vps-business — relay traffic is bursty (10–50 TB/month) but CPU is light because relayed bytes pass through TLS/AES-NI. Exit nodes are a different load profile: more L4 connection churn, more ARP table pressure, more abuse mail. We've put the abuse handling on a documented track (see /abuse/) so you know exactly what triggers a takedown vs. a heads-up email.

Jurisdictions

Recommended locations for Tor relay & exit hosting

Each location below has a specific legal or technical alignment with this workload — the others stay supported, but we suggest these first.

Iceland

Reykjavík (IS-RKV)

Free-press constitution, no MLAT, geothermal grid.

Tor relay & exit hosting in Iceland

Romania

Bucharest (RO-BUH)

Constitutional court rejected EU data retention twice.

Tor relay & exit hosting in Romania

Netherlands

Amsterdam (NL-AMS)

Tier-1 carriers, lowest median EU latency, AMS-IX peering.

Tor relay & exit hosting in Netherlands
Plans

Plans sized for Tor relay & exit hosting

Pre-filtered by CPU, memory and bandwidth profile. Pick the cheapest that fits your projected load — you can hot-resize later without downtime.

VPS

Growth

AMD EPYC 7443P
  • 4 vCPU
  • 8 GB DDR4 ECC
  • 120 GB NVMe
  • 2.5 Gbps unmetered
$26.99/mo
Deploy
VPS

Business

Intel Xeon Gold 6430
  • 6 vCPU
  • 16 GB DDR5 ECC
  • 240 GB NVMe
  • 5 Gbps unmetered
$39.99/mo
Deploy
Dedicated

Shield

AMD EPYC 7313P
  • 16 cores · 32 threads
  • 64 GB DDR4 ECC
  • 2× 1 TB NVMe
  • 1 Gbps unmetered
$79.00/mo
Deploy
Sysadmin FAQ

Tor relay & exit hosting — questions answered

Are exits really allowed in your chosen jurisdiction, or just unaccompanied silence?
Allowed in writing — see our /aup/. Exits run today across all four jurisdictions; abuse posture is public on /abuse/. We don't require notification before bringing one up, but we appreciate the heads-up so we can pre-empt support tickets if a downstream carrier escalates.
How much bandwidth does a meaningful Tor relay need?
A guard at 10 MB/s sustained moves about 25 TB/month; an exit at the same rate pulls 30–40 TB once you factor in the reverse-path traffic. All our VPS plans ship with unmetered uplinks (1–10 Gbps depending on tier); relays don't hit overage.
What happens when a downstream carrier complains about my exit?
We forward the complaint to your account email with our standard "Tor exit boilerplate" already attached. You ack within 48 hours; we don't take action unless the complaint is CSAM or a credible imminent threat. Same path as any other abuse contact — just a different reply template.
Can I run a hidden service (.onion) on the same node?
Yes. Hidden services don't generate abuse mail (they're inbound from the Tor network, not the open internet) so they're actually a softer load profile than relays or exits.
Do you publish your ASN, peers, and downstream carriers?
Yes — see /network/. AS59264 in Switzerland and Romania, mixed transit elsewhere; full peering matrix is public. You can trace from your own ISP to verify the path lands locally.
Other workloads

Run something else on the same hardware

Same network, same posture, same prices. Pick what you actually need to deploy.

Self-hosted VPN server

VPN server

Self-hosted mail server

Mail server

Bitcoin full node

Bitcoin node

Monero full node

Monero node

Lightning Network node

Lightning node

Matrix homeserver hosting

Matrix homeserver

Game server hosting

Game server

Offshore seedbox

Seedbox

Dev sandbox / CI runners

Dev sandbox

Tor relay & exit hosting — deploy in 60 seconds

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

Launch a server See the network