Best VPS for Tor Relays and Bridges (2026): Who Allows What, According to Their Own Policies and the Tor Project

A Tor relay is the easiest server to run and the easiest to lose. Middle relays and bridges generate almost no complaints; exits generate them by the dozen, and what happens next depends entirely on whether a person or a script reads them. The Tor Project keeps a community-maintained list of which hosts tolerate what; providers keep policies that sometimes agree with it.

This is a ranked list of ten hosts for Tor relays, bridges and exits, built from the providers' own pages and the Tor Project's Good/Bad ISPs list, with the hosts to avoid at the end. Every claim was re-checked in September 2026.

Updated September 2026. Ranking criteria, in order: does the provider say in writing that relays are welcome and how abuse is handled; exits allowed, and under what conditions; what signup asks for (a relay operator's identity is a target); payment privacy; price and bandwidth as tiebreakers. The Tor Project list is cited with its own "last updated" dates; where a provider's page says something different, the provider's page wins.

TL;DR: For relays and bridges with no identity attached, Servury. For exits with a long record, FlokiNET and 1984 Hosting in Iceland, Privex in Sweden, and IncogNET with a reduced exit policy. Avoid Contabo (blocks Tor outright), OVH (exits forbidden), Vultr and DigitalOcean (no exits) and be careful with Hetzner (abuse reports lead to locks).

Relay, bridge, exit: three different risks

  • Middle relays carry encrypted traffic between other relays. No complaints, modest bandwidth, allowed nearly everywhere that does not block Tor entirely. Your IP is public in the consensus.
  • Bridges are unlisted entry points for censored users. No complaints, low bandwidth, and your IP stays out of the public list. The cheapest useful thing you can run.
  • Exits send traffic to the open internet under your IP. Every abuse complaint the internet generates for that traffic arrives at your host. Exits need a host that has decided, in writing, to handle that, and a reduced exit policy helps.

The ten, ranked

1. Servury

Policy: relays and bridges are welcome, and the plan page says why they are workable: "abuse reports are read by a person before anything is actioned", with no automated suspension. Exits are not advertised; ask support before running one.

Signup and payment: nothing at signup; Monero, Bitcoin and six other coins on Servury's own nodes, a card, or cash by mail in any currency. No access logs, a signed warrant canary. That matters for relay operators specifically: the list of who runs which relay is public, and a host that knows nothing about you cannot add to it.

Price and places: from $9.99 on the Blackbox line (2 vCPU, 4 GB, 10 Gbps with 4 TB of transfer per 31 days, a routed /64, encrypted memory) in Montreal; standard-line locations in 7 more countries.

Honest limits: not on the Tor Project list yet (founded 2025), and no exit policy in writing.

2. FlokiNET (Iceland, Romania, Finland, Netherlands)

Policy: the Tor Project list marks bridges, relays and exits all allowed and notes FlokiNET sponsors exit nodes itself. Its homepage: "We do not require any personal details or identification. Any valid email address is enough."

Payment and price: Bitcoin, Monero, Ethereum, PayPal, bank transfer; from €3.50; DDoS protection included. Full comparison.

Honest limits: manual provisioning and no refunds.

3. 1984 Hosting (Iceland)

Policy: bridges, relays and exits allowed per the Tor Project list (updated May 2024, "free speech hoster", IPv4 only noted); a stated no-logging policy on VPS since 2006.

Payment and price: Bitcoin, Monero, cards; $9.66 for 1 CPU, 1 GB, 25 GB NVMe, 1 TB. Full comparison.

Honest limits: 1 TB a month is thin for a busy relay; Iceland's latency.

4. Privex (Sweden, Germany, US)

Policy: "Tor friendly hosting provider who runs 3 relays and an exit themselves", per the Tor Project list (June 2022); exits allowed in Sweden, restricted elsewhere; crypto required.

Payment and price: Bitcoin, Litecoin, Monero, Dogecoin, HIVE, EOS in-house; from $8.00. Full comparison.

5. IncogNET (US, Netherlands, Sweden, Bulgaria)

Policy: exits allowed if you "host a page on port 80 explaining the server is a Tor exit and use a reduced exit policy", per the Tor Project list (April 2023); Tor, I2P and Yggdrasil supported on its own pages.

Payment and price: Monero, Bitcoin, Litecoin, Dogecoin in-house, PayPal; from $4.62; email-only signup. Full comparison.

6. Njalla (Sweden)

Policy: bridges, relays and exits allowed per the Tor Project list (October 2023): "privacy-focused, accept cryptocurrencies".

Payment and price: Bitcoin, Litecoin, Monero, PayPal; VPS from €15 at our last full check; email or XMPP signup. Full comparison.

Honest limits: price per gigabyte of bandwidth; a domains company first.

7. OrangeWebsite (Iceland)

Policy: bridges and relays allowed and exits listed as probable on the Tor Project list; an explicit free-speech policy under Icelandic law on its site.

Payment and price: Bitcoin, Litecoin, cards, PayPal, cash by mail; from €22.40; email-only signup. Full comparison.

8. BuyVM / Frantech (Luxembourg, Las Vegas, New York)

Policy: "All relays fine if following steps. Notices ignored", per the Tor Project list (September 2021), exits included.

Price: KVM slices from $3.50 (1 GB, 20 GB) with 3.5 Tbps DDoS protection advertised; payment methods are not published on its site.

Honest limits: an account and, in practice, identifying details; the policy note is four years old.

9. netcup (Germany, Austria, Netherlands, US)

Policy: "Everything allowed that T&Cs don't exclude", exits included, per the Tor Project list (September 2021).

Honest limits: a mainstream German host with an identified account; cheap and fast, but it knows exactly who you are.

10. Linode / Akamai (multiple)

Policy: exits allowed with a reduced exit policy, per the Tor Project list (October 2021).

Honest limits: a card, identity checks, and an abuse desk that works from tickets. Fine for a well-behaved reduced exit; not a privacy host.

Avoid for exits, or entirely

ProviderTor Project list saysRelaysExits
Contabo"Entitled to immediately block TOR services" (July 2022)NoNo
OVH"Running Tor exit node is strictly forbidden" (September 2021)YesNo
Vultr"Don't allow exit relays per AUP" (October 2024)YesNo
DigitalOceanRelays yes, exits noYesNo
HetznerExits allowed but "abuse reports can lead to server lock" (September 2021)YesRisky
Scaleway (Online S.A.S.)On the avoid listListed yesListed yes
SporeStackIts own AUP: "a Tor relay (not an exit!)"YesNo

Running one well

  • Start with a bridge or a middle relay. Unmetered or generous bandwidth matters more than CPU; 2 vCPU and 2 to 4 GB is plenty.
  • Set MyFamily if you run more than one relay, and ContactInfo that reaches you without naming you.
  • For exits, use a reduced exit policy, serve an explanation page on port 80, and set reverse DNS that says "tor-exit". Most hosts that allow exits ask for exactly those.
  • Pay in a way that does not identify you if your threat model includes being identified as a relay operator; the consensus already publishes your IP.
  • Keep your own logs off. Tor does not log traffic; make sure nothing else on the box does.

Our no-KYC ranking covers the identity side of the same providers.

Frequently asked questions

Which VPS providers allow Tor exit nodes?

Per the Tor Project list and their own pages: FlokiNET, 1984 Hosting, Privex (Sweden), IncogNET (reduced policy), Njalla, OrangeWebsite, BuyVM, netcup and Linode (reduced policy). Servury welcomes relays and bridges; ask before an exit.

Can I run a Tor relay on a $5 VPS?

Yes. A middle relay or bridge needs little CPU or RAM; bandwidth is the limit. Check the monthly transfer cap before choosing.

Is running a Tor relay legal?

Running relays and bridges is legal in every jurisdiction on this list. Exits are legal too, but attract complaints and, occasionally, police interest directed at the IP; choose a host that has decided how to handle that.

Do I need to hide that I run a relay?

You cannot: relay IPs are public. What you can keep private is the link between the relay and you, which is a matter of how you signed up and paid.

Deploy
this

Compare
providers

More
articles