Our protocol, open source
WarrenGuard
The next-generation VPN protocol that blends into the web. Built on QUIC, designed obfuscation-first, released under the AGPL-3.0 license.
Why a protocol?
Classic VPN protocols encrypt, and that is fine. But they have an ugly flaw: they are recognizable. On a network, a WireGuard or OpenVPN connection has an identifiable signature from the very first packets. And what can be recognized can be blocked. I have no taste for digital captivity, whether it comes from hotels, airports, trains, cafes, surveillance-minded companies, or whole countries.
WarrenGuard turns the problem around. Instead of encrypting and then trying to hide, it is built from the ground up on QUIC, the protocol that already carries a huge share of the modern web. To an outside observer, a Warren connection looks like ordinary HTTP/3: the same traffic your browser produces when you watch a video.
Obfuscation is therefore the protocol itself: there is no stealth mode to switch on in the settings.
What it changes for you
- Where classic VPNs are blocked, Warren keeps going: your traffic shows nothing that sets it apart from everyday browsing.
- Modern encryption across the tunnel: TLS 1.3, the standard that already protects your bank and your email.
- Every exit server identifies itself with a cryptographic key your app verifies directly, with no certificate authority and no trusted third party.
Under the hood
These are the technical choices that determine WarrenGuard. They are detailed in the white paper.
- QUIC transport: packets travel one for one in DATAGRAM frames, and a lost packet never delays the ones behind it. Reliable streams are used only for the handshake.
- TLS 1.3 only handshake: a server identity is its Ed25519 key, verified directly by your app. No certificate authority, so none to compromise.
- SNI-split on by default: the ClientHello is split across two packets, so a passive observer cannot extract the domain name. And no client certificate is requested: nothing to spot by active probing.
- Optional cover-domain mode: the server presents an ordinary certificate (think Let's Encrypt) for a plausible domain; the Warren identity is proven inside the tunnel.
- Sealed multi-hop: your traffic is encrypted for the exit server before it crosses a relay that cannot read it. The exit sees the relay, never your IP. Built into the engine, rolling out across the network.
- DAITA available: a defense that scrambles the shape of your traffic to defeat AI-guided analysis, negotiated per session.
- QUIC connection migration on the relay hop: you move from Wi-Fi to cellular without a drop. Disabled on the exit, so your network changes cannot be used to correlate you.
- The code is public: anyone can read, audit and build the engine.
The code is public
WarrenGuard is released under the AGPL-3.0 license. Shared test vectors (the golden vectors) guarantee every implementation produces exactly the same bytes.