Skiff 2
- vCPU
- 1 × shared
- RAM
- 2 GB
- Storage
- 40 GB NVMe SSD
- Transfer
- 3 TB
- IPv4 / IPv6
- 1 / /64 routed
Solution
A Tor middle relay runs comfortably on one shared core and 1 GB of RAM; the constraint is bandwidth and the provider's tolerance. Relays and bridges are welcome on every OnionVPS instance. Exit nodes are permitted only in specific jurisdictions and only with a published abuse contact, because an exit node will attract complaints about traffic that is not yours.
| Resource | What you actually need |
|---|---|
| CPU | 1 core per ~100 Mbit/s of relayed traffic (AES is the bottleneck) |
| RAM | 1 GB for a middle relay, 2 GB for a guard |
| Transfer | 4 TB and up — relays consume everything you give them |
| Policy | Bridges and middle relays everywhere; exits in approved regions only |
Location is usually the decision that matters most for this workload — either because latency dominates, or because jurisdiction does.
Iceland and Switzerland are the strongest legal ground.
The distribution package lags; use deb.torproject.org.
ORPort 443, ExitRelay 0, and a ContactInfo line you actually read.
AccountingMax keeps a relay inside your transfer allowance rather than surprising you.
Watch the relay on Tor Metrics; consensus weight takes several days to build.
In approved jurisdictions, yes, with a published abuse contact and a reduced exit policy. Exits generate complaints about traffic that is not yours, so we require that you are prepared to answer them. Middle relays and bridges are unrestricted everywhere.
Not here. Middle relays and bridges carry no exit traffic and generate no complaints; they are a normal workload on this platform.
As much as you allow. A relay with 4 TB a month and an AccountingMax setting is a genuinely useful contribution to the network.