FAQ

No. We run one WireGuard tunnel — for our own company — and don't have the bandwidth to carry anyone else's traffic. And honestly, you shouldn't fully trust someone else's VPN anyway, ours included. So instead of selling you access, this page hands you the guide and the source to run your own. It's free.

If you can copy-paste into a terminal, you can do this. Rent a $4–6/month VPS, run one script (wg-setup.sh), then add each device with another. About ten minutes end to end. The setup guide walks every step, and there's a manual "by hand" version if you'd rather understand each command.

Three things: a server with a public IP (any cheap VPS, or a spare machine on a connection you control), root access on it, and the free official WireGuard app on your phone or laptop. That's it — no account with us, nothing to buy from us.

It removes the middleman. A commercial VPN asks you to trust their "no logs" and pools your traffic with thousands of strangers on shared IPs (which is why they get blocklisted). On your own server, the only operator is you, the logging policy is whatever you set (keep none), and the exit IP is yours alone. It's not magic — see the anonymity question below — but the trust stops with you.

WireGuard is a fraction of the code (~4,000 lines vs. hundreds of thousands), uses only modern, fixed cryptography, connects faster, and uses less battery. Less surface area means fewer places for bugs or misconfiguration to hide. It's in the Linux kernel and every major OS has a first-party app.

Yes. The config builder creates your keypair in your browser using the platform's cryptography, and the private key stays on your device — it goes into your .conf and nowhere else. The tool makes no network requests at all; you can load the page, go offline, and it still works.

It moves the point where your traffic exits, encrypts the hop from your device to your server, and stops your local network and ISP from seeing your destinations. It is not anonymity software — for that, use Tor. A VPN shifts trust from your ISP to whoever runs the server; the whole point of running your own is that "whoever" is you.

Yes — that's a "split tunnel." Change the AllowedIPs line in the client config (or pick "Split tunnel" in the builder). The guide has the exact values.

Three things, in order: (1) is udp/51820 open at your host's cloud firewall / security group, not just the box's own firewall? (2) is IP forwarding on (wg-setup.sh does this)? (3) does the client's Endpoint match the server's real public IP and port? Run sudo wg show on the server — a recent handshake means it's working.

Yours. It's your machine and your exit IP, so you're accountable for the traffic that comes out of it — and so is your VPS host under their terms. Follow the law and your provider's acceptable-use policy, and don't route anything through it you wouldn't sign your name to.