Hello World: Why OpenFreeNet Exists
Today we’re publishing the first version of OpenFreeNet, and this site.
The problem
Most “VPN” services today are a centralized proxy with a slick marketing site on top. Your traffic is decrypted, logged, and analysed by the operator, and there’s no way to verify otherwise. Some operators do it well; some don’t. Either way, the trust boundary is the same: you hand over your traffic and hope for the best.
That’s a poor fit for teams.
What we built instead
OpenFreeNet is a gateway mesh VPN. Instead of a single proxy hop, your traffic is routed across a pool of independently operated gateways that share a control plane but no per-user state. Each gateway only knows about the peers currently routed through it; once your session ends, that state evaporates.
Concretely:
- WireGuard-grade encryption, end to end. The operator can see connection metadata but not packet content.
- No persistent user records at the edge. Gateway state is ephemeral and scoped to the active session.
- A control plane you can audit. The panel is open source; the agent is open source; the node protocol is documented.
- Subscription URLs that rotate. If your link leaks, you invalidate it in one click.
What’s on this site
We’ve shipped the Docs alongside the launch, installation, quickstart, subscription management, and an FAQ, in English and Simplified Chinese.
We’ll also be publishing deeper technical articles here regularly, starting with WireGuard vs OpenVPN and What is a Gateway Mesh VPN. Subscribe to the RSS feed if you’d like to follow along.
If you’re a team evaluating VPN infrastructure, the Quickstart walks you from zero to a working tunnel in under five minutes.
- The OpenFreeNet team