Next Uses: Seven Places Where a Network per Program Could Fit
AI coding agents were the first use for a network per program. Seven more could use the same core and plugins, and none of them has been tried yet.
Each of these needs the same few things: one program sealed in, a path chosen for it, a policy, a record. What differs is which plugin would carry the use-specific part, and that’s the point of the platform: the core stays the same.
The list is a set of guesses to test, not claims.
CI Jobs and Package Installs
A build step pulls dependencies from wherever its lock file says, and an install script can run anything. A policy per job, drafted from a clean build, makes a poisoned dependency’s call home fail the build. vpnw’s exit code 120 already does that.
MCP and Tool Servers
Tool servers that agents call run with the user’s network. Each could get its own policy: the search tool reaches the search API and nothing else.
Browser Agents
A browser agent reaches the open web by design, so an allow list is too tight. A Guard plugin with a blocklist and deny_private, which keeps it off the local network and cloud metadata, fits better.
Crawlers That Need a Regional Exit
A crawler that must appear from one country can go through a WireGuard tunnel to that region, run inside vpnw, while everything else on the server keeps its own network. That works since 0.4.0. Since 0.7.0 it can also leave through vpnw exit on a server in that region, from an address of its own, with its policy checked again there. Exit Since 0.8.0 it can rotate through a folder of that region’s WireGuard configs, moving on every so often and whenever one stops answering. Rotate
Platforms That Host Other People’s Agents
A platform running many customers’ agents needs one policy per agent and a record per customer. That’s the core plus an Observer that sorts records by tenant.
Audit Trails in Regulated Teams
“Where did this agent send data?” needs an answer an auditor believes. That’s Ledger, back in 0.5.0 as an Observer plugin that seals each run’s record, with a check that names any line someone changed. Ledger
Everyday Developer Tools
Editors, language servers and CLIs talk to more hosts than most people know. vpnw trace shows which, in a minute.
Which Come First
CI and crawlers can be tried as VPN Works is now, and audit trails since 0.5.0. Platforms need a plugin that doesn’t exist yet. Anyone with one of these uses is welcome to write.