HSProxy: a dedicated SOCKS proxy over Tor

HSProxy is a SOCKS proxy dedicated to one customer and reached over its own Tor onion service. Your traffic passes the same three Tor relays as ordinary Tor use, but there is no exit node. The connection terminates on a machine reserved for you, which connects to the internet from a clean clearnet IP address that nobody else uses.

# what the path actually looks like
relays     3 · guard, middle, rendezvous
exit node  none · the far end is your machine
exit ip    dedicated · clean · replaceable
transport  SOCKS · nothing encapsulated
leaks      no route out

No exit node is the whole point

Public Tor exits are shared by everyone, so they inherit everyone's reputation. Services throttle them, block them outright, or bury them under CAPTCHAs you can never quite finish. That is the experience most people mean when they say Tor is unusable.

HSProxy has no exit node. Your traffic reaches a rendezvous point and lands on a machine dedicated to you, which makes the outbound connection from its own clean address. Nothing about that address is shared, and it can be replaced on request.

Nothing is encapsulated either. The application stream terminates at the SOCKS boundary and Tor carries it onward as relay cells, so there is no second TCP stack to collapse under packet loss, and no route exists outside the proxy for DNS, IPv6 or WebRTC to escape through.

  • path3 Tor relays, then your own machine
  • exitDedicated clearnet IP, never shared
  • transportNo nested TCP, so no meltdown under loss
  • leaksNo route outside the proxy at all

Three ways to route your traffic

Every option below is a real trade between speed, exposure, and who has to be trusted. Read them in order: each one answers a problem the previous one leaves open.

Commercial VPN: your traffic crosses one relay shared with every other customer. That machine terminates your connection and originates the outbound request, so its operator sees your address and your destination together. Throughput is high, anonymity is none, and the exit addresses are published VPN ranges.
Figure 1 — Commercial VPN
VPN over Tor: three Tor relays and then a VPN server. The guard sees your IP, and both entry and exit are public relays, so watching them together correlates the traffic. A TCP tunnel inside Tor's own TCP means one lost packet stalls both. Throughput is low, anonymity is medium.
Figure 2 — VPN over Tor

Everyone accepts the trade: privacy costs you speed. We removed it. The same three relays as ordinary Tor, no exit node at all, and a clean clearnet IP that belongs to one customer.

HSProxy: three Tor relays to a rendezvous point, then a machine dedicated to you. There is no Tor exit node, so none of the throttling, blocking or CAPTCHA walls that public exits attract applies. Nothing is encapsulated, so there is no second TCP to collapse and no route outside the proxy for anything to leak through.
Figure 3 — HSProxy
Black Box: on an ordinary VPS the host reads guest memory and the disk sits in plaintext. With AMD SEV-SNP the memory is encrypted under a key held in the CPU and integrity-protected, and with LUKS2 full-disk encryption a seized disk is inert. You hold root, so the no-log policy is something you verify rather than believe.
Figure 4 — Black Box

Where it is the wrong tool

Worth saying plainly, because the honest limits are short: HSProxy is slower than a plain commercial VPN, and it carries no UDP. If you want to stream video or pull large downloads, it is not the right choice and we will tell you so.