Middle relay
Forwards encrypted traffic within the Tor network. It is not the endpoint that connects to public websites.
A Linux server for a non-exit relay or an obfs4 bridge, with full root and transfer allowances from 2 TB to 16 TB. Choose the capacity you want to contribute, then configure Tor to stay inside it.
A Tor middle relay forwards traffic inside the Tor network; a bridge offers an entry point that is not publicly listed like ordinary relays. Both require capacity planning, updates and provider permission. SilentVPS's planned catalogue excludes exit nodes, which have different operational responsibilities.
Forwards encrypted traffic within the Tor network. It is not the endpoint that connects to public websites.
An entry relay that is not published in the ordinary public directory. An obfs4 transport can help users on filtered networks reach Tor.
Connects to the public internet on behalf of Tor users. Its IP receives the associated complaints and exposure. Exit nodes are excluded from the planned service.
A modest relay is still useful. Transfer allowance and sustained connectivity usually matter more than disk capacity. Veil provides 2 TB, Shade 4 TB, Eclipse 8 TB and Obsidian 16 TB per month; leave some room for updates and other traffic.
Use Tor’s RelayBandwidthRate, RelayBandwidthBurst, AccountingMax and accounting-period settings to fit the allowance. Confirm how inbound and outbound transfer are counted before setting your budget. A burst rate is not the same as a guaranteed sustained port speed.
Start with Debian or Ubuntu and follow the Tor Project relay documentation for the current package and configuration.
Choose a relay nickname and safe operator contact. Do not insert a personal identifier merely because the example configuration has one.
Enable bandwidth accounting, watch health and resource usage, and allow time for a new relay to earn network weight.
Apply security updates, preserve relay identity keys securely and plan restart windows.
Use a dedicated account alias and consider the public transaction history of the wallet you use for payment. Tor-aware browsing and an SSH onion endpoint can reduce exposure in the management path. The server’s relay identity itself is intentionally public for an ordinary middle relay.
A relay, bridge and onion service are separate roles. Hosting a private application behind an onion address does not automatically make the machine a relay, and running a relay does not automatically hide an application’s origin.
Monthly or annual billing, with 30% off the twelve-month total when you pay yearly. Prices are in USD; cryptocurrency amounts depend on the invoice exchange rate. Full root, KVM virtualization, NVMe, IPv4 and IPv6 are part of the target specification for every tier.
$13/month · $109.20/year. 1 vCPU, 2 GB RAM, 30 GB NVMe and 2 TB monthly transfer. A compact starting point for one lightweight service.
$33/month · $277.20/year. 2 vCPU, 4 GB RAM, 80 GB NVMe and 4 TB monthly transfer. More room for applications and everyday self-hosting.
$63/month · $529.20/year. 4 vCPU, 8 GB RAM, 160 GB NVMe and 8 TB monthly transfer. Space for a larger stack or transfer-intensive workload.
$118/month · $991.20/year. 8 vCPU, 16 GB RAM, 320 GB NVMe and 16 TB monthly transfer. The largest configuration for dense services and heavier compute.
Choose the resources you need. Keep the personal details you don’t need to share.