Are middle relays and bridges allowed on every plan?

Yes — every VPS, dedicated, and storage plan permits non-exit Tor relays without notice. We ask that you cap advertised bandwidth at 70% of plan port speed to leave headroom for normal operation.

How do I get approval to run an exit relay?

Open a ticket from your client area with your planned exit policy and abuse-handling commitment. Approval is usually same-day for the recommended jurisdictions and uses the Reduced Exit Policy as a baseline.

What happens when an abuse complaint arrives?

We forward the complaint to your registered abuse contact and pause action for five business days while you respond. Tor-recognized exits are not summarily terminated, and we maintain a documented escalation track that recognizes legitimate exit operation.

Do you allow Snowflake or obfs4 bridge operation?

Yes — Snowflake proxies and obfs4 bridges run on any plan. They generate no abuse traffic and are not jurisdiction-sensitive. VPS-1 is sufficient for most bridges.

Can I run a Tor onion service for my own application?

Yes. Onion services run cleanly on KVM. We can provide a dedicated IPv6 / no-IPv4 instance specifically for onion-only services, which simplifies the OPSEC posture.

How much bandwidth do you advertise as a relay-friendly host?

We do not advertise per-customer bandwidth caps for Tor traffic specifically. The plan's monthly bandwidth allowance applies; relays running at 200 Mbps sustained on VPS-4 fit comfortably within the 6 TB allowance.

Use caseTech-heavy

Offshore hosting for Tor Relay & Bridge — DMCA-resilient & privacy-first

Run a Tor middle relay, exit, or obfs4 bridge from a privacy-friendly jurisdiction.

Explore plans Talk to sales

Tor-friendly AUP
1 Gbps unmetered
Multi-jurisdiction
Plausible analytics only

Quick factsTech-heavy

Plans4recommended

Jurisdictions4best fit

Tor-friendly AUP
1 Gbps unmetered
Multi-jurisdiction
Plausible analytics only

The case

Why offshore for tor relay & bridge hosting

Exit relays generate abuse traffic that mainstream hosts terminate without dialogue. Privacy-friendly jurisdictions and a host with a documented exit-operator policy preserve the Tor network instead of attriting it. Middle relays and bridges are uncontroversial and welcome anywhere on our network.

Tor-friendly AUP

1 Gbps unmetered

Multi-jurisdiction

Privacy-friendly billing

What matters

Specs that move the needle

The four hardware and network attributes that decide whether a tor relay & bridge hosting workload runs smoothly.

1 Gbps unmetered

Symmetric port — both upstream and downstream.

No content logging

Plausible analytics only; no per-customer access logs.

Multi-jurisdiction

8 locations to spread bridge / middle / exit relays.

Tor-friendly AUP

Allowed under fair-use AUP across all jurisdictions.

Hardware

Plans we'd pick for you

Engineered for tor relay & bridge hosting workloads — pre-warmed by customers running this exact use case.

VPS-1

Entry-level KVM VPS, anonymous & DMCA-resistant.

CPU1 vCPU (AMD EPYC)

RAM2 GB DDR4 ECC

Storage25 GB NVMe SSD

Bandwidth1 TB / month

DDoS10 Gbps

IPv41 included

Full root access (KVM)
10 Gbps DDoS protection
IPv4 + IPv6
Provisioned in < 5 min

VPS-2

Workhorse offshore VPS for small projects.

CPU2 vCPU (AMD EPYC)

RAM4 GB DDR4 ECC

Storage60 GB NVMe SSD

Bandwidth3 TB / month

DDoS10 Gbps

IPv41 included

2 vCPU AMD EPYC
4 GB ECC RAM
60 GB NVMe storage
10 Gbps DDoS shield

VPS-4

Mid-tier offshore VPS — sweet spot for production.

CPU4 vCPU (AMD EPYC)

RAM8 GB DDR4 ECC

Storage120 GB NVMe SSD

Bandwidth6 TB / month

DDoS20 Gbps

IPv41 included

4 vCPU / 8 GB RAM
20 Gbps DDoS protection
Free weekly snapshot
Provisioned in < 5 min

VPS-8

Heavy-duty offshore VPS for traffic-heavy projects.

CPU8 vCPU (AMD EPYC)

RAM16 GB DDR4 ECC

Storage240 GB NVMe SSD

Bandwidth10 TB / month

DDoS40 Gbps

IPv41 included

8 vCPU / 16 GB RAM
40 Gbps DDoS shield
240 GB NVMe SSD
Daily snapshots included

View all 35 plans

Geography

Best jurisdictions for this workload

Pick the location that matches your latency, privacy, and legal-posture requirements.

What we don't do to you

Built for people who actually care about privacy.

Four commitments that hold across every plan, every jurisdiction, and every payment method — including when you host tor relay & bridge hosting. They're what makes offshore offshore.

We don't process DMCA takedowns

The DMCA is a US statute. None of our 8 operating jurisdictions are inside US territorial scope. Boilerplate, automated, or speculative takedown notices go to /dev/null. Substantive complaints under local law route through counsel, with a 5-business-day customer-response window.

No KYC. Ever.

No name, no phone, no government ID, no proof of address — at any point, regardless of order size. Sign up with a pseudonym and a password. Email is optional. No KYC for crypto-paid customers, no KYC for card-paid customers (we use Card2Crypto for the card rail to bypass merchant KYC).

Zero logs. Nothing to hand over.

We don't keep server-side logs of customer activity — no access logs, no IP logs, no command-history logs. Tax / billing records follow Seychelles law (7 years, billing-only — never linked to traffic). No third-party trackers, no analytics linked to your account, no data brokerage on any tier. See our transparency report for how many subpoenas this has translated into 'nothing to produce'.

Crypto-native checkout, refunds included

Self-hosted BTCPay Server — no Coinbase Commerce or third-party processor in the loop. 12 cryptos accepted: Bitcoin, Lightning, Monero, Ethereum, USDT, USDC, Litecoin, Dash, Zcash, Solana, TON. 7-day money-back guarantee, refunds settle in the original payment currency within hours.

Acceptable Use Policy·Privacy Policy·How abuse handling works

FAQ