Releases on VPNW.com

VPN Works 0.4.0: WireGuard Tunnels for One Program at a Time, Without Root

Fri, 09 Oct 2026 00:00:00 +0000

VPN Works 0.4.0 sends one program through a WireGuard tunnel and leaves the rest of the machine alone. vpnw runs the tunnel itself, inside its own process, so it needs no root, no kernel module and no network interface.

Give vpnw the WireGuard config your VPN provider or your own server hands out, and the program you name goes through it:

vpnw guard --wireguard office.conf --policy agent.toml -- ./my-agent

Everything else on the machine keeps its usual network. The program is sealed in, so it can’t go around the tunnel, and every connection it makes is still checked against the policy and written down.

VPN Works 0.4.1: All 17 Ways Out of the Sealed Sandbox Blocked, IPv6 Included

Fri, 09 Oct 2026 00:00:00 +0000

VPN Works 0.4.1 adds no features. It closes the one gap the 0.4.0 tests left open, and it fixes a bug those same tests turned up along the way.

The gap was IPv6. A sealed program tries every known way around vpnw, and two of those ways go over IPv6. The machine that records the project’s figures has no IPv6 in its kernel at all, so those two tests never ran. 0.4.0 said so: 14 of 14 blocked, 2 not run.

VPN Works Rebuilt as One Core With Plugins: What Moved Where in 0.3.0

Fri, 09 Oct 2026 00:00:00 +0000

VPN Works started as five separate engines that each worked and didn’t add up to one thing. Version 0.3.0 rebuilt it from scratch as one small core, vpnw, with plugins for everything else.

The five engines of September were the Agent, Scope, Lab, Ledger and Exit. Each had its own binary, its own command line and its own browser demo. Underneath, the Agent’s code was already shaped like a core: a broker that takes every connection, a policy, paths, and one event model that everything spoke. What was missing was a way for everything else to plug into it.