Tor Relay VPS — Middle, Bridge, Exit, No KYC
Run a Tor relay or exit on a no-KYC VPS from $3* (fund $50+; Nano list $3). Iceland or Romania. You operate the daemon from Tor Project docs.

Rent a VPS, follow the Tor Project relay guide, and publish a contact. Exits need an abuse path. BitCloudVPS does not run Tor for you.
What operators actually run
Tor Project: relay operations is the checklist: package, ORPort, contact, and MyFamily if you have more than one. Middle relays and bridges are the usual start. Exits are allowed on request; expect abuse mail and answer it. Paying the VPS in crypto does not change the AUP.
Business $24/mo (6 vCPU / 16 GB DDR5) is the production size. Crypto invoice, no KYC.
Launch nowPlaybook
- Plus or Business for a middle relay. High-bandwidth exits want Pro / Max or dedicated.
- Install from Tor Project: relay operations. Set ContactInfo. Do not hide an exit.
- Iceland or Romania are the usual flags. Amsterdam is faster peering and a different process story.
- Unmetered is not a license to ignore L7 tickets you cannot explain.
Limits
CSAM and attacks still come down. You run the relay with root; BitCloudVPS rents the box and handles abuse mail to the host.
Middle relay economics: which plan serves bandwidth honestly
A Tor middle relay is a bandwidth donation wrapped in a daemon, and the plan choice is a bandwidth-choice: Plus $13.50/mo (2.5 Gbps unmetered) or Business $30 list / $24 yearly (5 Gbps) are the usual middle-relay tiers, because Tor's own consensus weights relays by sustained throughput and an unmetered port is what lets you contribute it without an overage bill. The install is the Tor Project's relay guide — package, ORPort, ContactInfo, MyFamily if you run more than one — and BitCloudVPS's part is the boring half: a stable IPv4, a /64 IPv6 block so the relay speaks both, ECC RAM, and L3/L4 DDoS included. Location is a real decision: Iceland and Romania are the community defaults for posture; Amsterdam buys the best peering; exits are allowed on request with a documented abuse path. No KYC, 19-coin checkout. Deploy in 60 seconds
Running an exit: what you accept, what the host does
An exit relay publishes your IP as the last hop of thousands of strangers' connections, and the honest contract is this: you run it with root, you answer the abuse mail it generates, and you set an exit policy that limits the ports you are willing to carry — the Tor Project docs cover reduced exit policies for exactly this reason. Exits are allowed on request within the AUP; expect the mail and answer it, because hiding an exit is the one thing that gets a relay removed fast. Higher-bandwidth exits want Pro ($45 list, $36 yearly, 5 Gbps) or Max ($60/$48, 10 Gbps) — consensus weight follows measured bandwidth, so the port size is the donation. Bridges and middle relays carry none of this weight and are the right start for most operators. The AUP's hard lines — CSAM, attacks — come down the same on a relay as on any box. No KYC, XMR and BTC both fine, deploy about a minute.
Where the limits are (October 2026)
Keep the threat model precise. Anonymous-adjacent hosting removes the host-side identity trail: token-only signup, optional email, no KYC review, crypto invoices that record a txid rather than a name. It does not blind the host to traffic it must carry, it does not make a logged-in panel session anonymous, and it does not protect workloads that identify themselves — an admin login from your home IP defeats the whole design. Exact limits of no-KYC anonymity. OPSEC guide. Full checklist. Payment-side note: chain analysis happens on public blockchains, not at the host. Coin choice and network choice are your OPSEC knobs, and the checkout keeps 19 of them open.
Exits?
Yes, on request, within the AUP.
Do you run the relay?
No.
Can I run a Tor exit node and pay with Monero?
Exits are allowed on request within the AUP, and XMR is one of 19 checkout assets with no KYC. You operate the daemon, set the exit policy, and answer abuse mail; BitCloudVPS provides the unmetered rack and handles abuse mail to the host.
How much bandwidth does a useful relay actually push?
Enough to matter needs sustained throughput, which is why the unmetered ports matter: Plus (2.5 Gbps) or Business (5 Gbps) are the usual middle tiers, Max (10 Gbps) for serious contributions. Tor weights your relay by measured bandwidth, not advertised intent.
Which plan size fits a Tor middle relay?
A Plus or Business VPS is the usual start for a middle relay or bridge. High-bandwidth exits are a different class — they want Pro, Max or dedicated metal, are allowed on request, and should expect and answer abuse mail. Set ContactInfo, and MyFamily if you run more than one relay.
What does the host actually know about me?
Whatever you hand over: a signup token, an optional email address, the invoice you paid and the service traffic. No ID documents, no phone number, no KYC step exists to hand anything else over.
What won't an anonymous VPS protect against?
Self-inflicted links: personal logins from a home IP, leaked cookies, services that publish your address, and on-chain patterns that tie wallets together. The server removes one identifier; it does not fix operational mistakes.
Primary sources
Ready to launch?
Configure a VPS or dedicated server, set a password, then pay the invoice.
Network
Edge RTT
Uptime · 36h
Complaints · 36h