All systems operational 12 elite locations · Europe & Asia Pay with crypto · 0 KYC
Home / Tor exit node VPS — bandwidth is cheap, the mailbox is the job
Tor · Exit

Tor exit node VPS — bandwidth is cheap, the mailbox is the job

Tor exit node VPS on VPSbit - exit policy by ticket, dedicated IPv4

Run a Tor exit on Titan: unmetered 10 Gbps from $19.20/mo annual-eff, allowed by ticket with a published abuse contact. Policy, abuse templates, mail volume.

Short answer

Run a Tor exit on Titan: unmetered 10 Gbps from $19.20/mo annual-eff, allowed by ticket with a published abuse contact. Policy, abuse templates, mail volume.

12 locations · 19 coins · SLA 99.95% · no KYC · public canary

VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.

Launch now

Exits run by ticket — here is the deal in full

An exit is allowed on this catalog, on one condition stated in the AUP: a ticket first and a working abuse contact published in the relay's ContactInfo. The practical tier is Titan — 8 vCPU EPYC, 32 GB ECC, 320 GB NVMe, unmetered 10 Gbps — $24 list, $19.20/mo annual-eff; dedicated Summit ($89 / $71.20) is the step when the exit deserves its own 10 Gbps metal. Signup is a token or email; the invoice takes nineteen coins; connection metadata is kept at most 24 hours.

An unmetered port never excuses an unanswered L7 ticket — that line is in the playbook because it is the usual failure mode, not because exits are discouraged.

The abuse mailbox: expectations and a working template

Exits receive abuse mail — that is the job. Reduce it at the source with the Tor Project's recommended settings: an exit policy that blocks SMTP ports (25, 465, 587) and the usual scan-magnet ranges cuts most complaints before they exist. For the mail that arrives, a plain template works: cite the relay fingerprint, state the reduced exit policy, link Tor Project's own exit-relay documentation, and close with the promise that specific evidence will be reviewed within 48 hours. Answer every serious complaint; ignores become deplatforming.

Run ReducedExitPolicy, keep the relay in the guide's recommended hygiene — MyFamily, separate NICs if you also run a middle, metrics review — and put the same abuse address in ContactInfo and in the ARIN/rDNS text you control via the editable PTR.

Flags and honest costs

PlacementExit realityCost
Reykjavikno-retention flag, +20%, speech-protectiveTitan ~$28.80 annual-eff
Amsterdambase price, dense peering, real mail cultureTitan $19.20 annual-eff
Metal step-upSummit for solo 10 Gbps$71.20 annual-eff

Honest framing: an exit advertises the rack's IP to the whole internet as the origin of everything, so the threat model is the facility's process, not your signup form. The dedicated playbooks for the two real flags: Iceland and the Netherlands.

Titan exit — 10 Gbps unmetered, $19.20/mo annual-eff, by ticket.

Open checkout

The exit ticket, field by field

What the ticket needs: relay fingerprint once generated, planned bandwidth, the exit policy (ReducedExitPolicy is the accepted default), and the abuse contact that will appear in ContactInfo. Approval turns on the mailbox being real — a plain self-hosted mail box on the same account works, as long as it answers within the 48-hour window the playbook promises.

Re-approval is not a ritual: policy changes, bandwidth jumps or a pattern of unanswered complaints reopen the conversation, and the AUP's abuse clauses outrank the exit permission.

Running middle and exit as a pair

The standard scaling pattern is two boxes: a Titan exit on the ticket, plus a middle or bridge on Core or Prime absorbing directory and relay traffic. Separate flags reduce correlated process risk — an Amsterdam exit with a Reykjavik middle is the common pair; both bill on the same token account.

Exits attract floods as well as mail: L3/L4 filtering ships in every tier and the no-KYC VPS with DDoS ranking compares the shield story across the market, dated.

More rankings and guides

Can I run a Tor exit node on this host?

Yes, by ticket: open a support request stating the exit plan, publish a working abuse contact in ContactInfo, and the AUP's exit terms apply from approval.

Which plan fits a Tor exit node?

Titan at $19.20/mo annual-eff — unmetered 10 Gbps is the exit's whole budget line; Summit metal is the step when the relay saturates a shared 10G.

How much abuse mail does an exit actually get?

Volume depends on the exit policy: blocking SMTP and scan-magnet ports in the reduced policy removes most complaints; what arrives should be answered within 48 hours on the template.

Why is an exit riskier than a middle relay?

The exit IP is the origin every destination sees, so complaints and legal interest land on the facility's jurisdiction — middle relays never present that surface.

Do exits need KYC here?

No — the account stays token-or-email and the invoice settles in nineteen coins; the abuse contact you publish is the public identity, not an ID document.

Primary sources

Ready to launch?

Build the box — VPS or bare metal — create the password, pay the invoice that follows.