No logs

Our VPN servers never save data that can be used to identify a customer.

Chaining supported

Don't trust that we're not logging?
Use multihop to connect to another VPN (or Tor) before you connect to us.

All server-side configs are public

Available for review here.

Security through transparency

(too many) details on how the network operates available on our blog and on our
privacy policy page.

Hashed tokens

Access tokens are hashed before connecting. Compromised/confiscated servers can't be used to identify clients.

Financials in several regions

No central office, anywhere.

• exploit mitigation
• hardened against heap corruption

• Mandatory access control
• Privilege seperation

• tripwire used to prevent backdoors

• Secure PKI management
• Confiscating one server won't compromise the rest

encrypted DNS servers

Chain DNS traffic with Anonymized DNS

DNSCrypt v2

Public DNSCrypt servers for encrypting your DNS traffic before you connect

Transparent .onion/.i2p access

Direct access to darknets

DNS/WebRTC leak protection

Stops IP leaks

DNS-based ad/tracker blocking

Prevents malicious trackers from working

Kill switch included

Many different killswitches available to prevents leaks if disconnected

SSH/HTTPS tunneling

Make your traffic look like SSH or HTTPS

Connect on any port

UDP or TCP (1-29999)

BitTorrent allowed

Port forwarding supported
Safe from the Port Fail vulnerability

No data caps, no throttling

(except on our free service)

Redundant load balancing

Minimizes downtime