Archive
2026
- VPN Works 0.8.0 Adds Tunnel Plugins and Rotates Through a Folder of WireGuard Configs
- VPN Works 0.7.0 Adds Exit With Fixed Addresses and a Second Policy Check at the Far End
- VPN Works 0.6.0: Lab Breaks the Tunnel on Purpose, and Four Fixes Come Out of It
- VPN Works 0.5.0: Ledger Seals Each Run's Record and Names the Line Anyone Changed
- Why the Project Is Called VPN Works When It Isn't Another VPN App
- VPN Works Rebuilt as One Core With Plugins: What Moved Where in 0.3.0
- VPN Works 0.4.1: All 17 Ways Out of the Sealed Sandbox Blocked, IPv6 Included
- VPN Works 0.4.0: WireGuard Tunnels for One Program at a Time, Without Root
- How VPN Works 0.4.0 Was Tested: 121 Tests, a Real WireGuard Peer and 14 Ways Out Blocked
- Tampered Log Case Study: 12 of 12 Edits to an AI Agent's Sealed Record Caught at the Exact Line
- Fixed Exit Case Study: A Stolen Agent Token Reaches Nothing Its Policy Refuses, Even Sent Straight to the Exit
- DNS Leak Case Study: A Stand-In VPN Client Sends 81 Queries to the Home Router While It Reconnects
- Where the Money Is in VPN Works: One Policy for Every AI Agent, and Least-Privilege Access on the Company VPN
- VPN Works Explained: How vpnw Gives Each AI Agent Its Own Network, and How Scope Narrows the Company VPN
- The Next VPN Works Prototypes: A 14-Week Beta for AI Agents and a Real Gateway Pilot for Scope
- Stolen VPN Login Case Study: Rules Learned From Two Weeks of Traffic Stop 136 of 144 Attempts
- Sealed Sandbox Case Study: A Script That Ignores Proxy Settings Tries Three Ways Out and Finds None
- Office Route Case Study: Ticket Filed Through the Office Exit, With the Deploy Token Still Blocked
- Next Uses: Seven Places Where a Network per Program Could Fit
- Introduction
- How It Works
- Coding Agent Case Study: Deploy Token Blocked by a Policy Drafted From One Traced Run
- Cloud Metadata Case Study: Request for Instance Credentials Blocked Before Any Connection Is Made