A normal VPN is one big pipe. Everything on the machine goes through it, with the same rules, and nobody records what each program actually did. That was fine when the only thing on the network was a person with a browser. Now it’s AI agents, scrapers and build jobs, each of which should get narrow network access and leave a record of every connection it made.
VPN Works rebuilds the VPN as an operating system. Its kernel, vpnw, handles network paths the way an OS kernel handles hardware. It seals a program in, decides every connection the program tries to make, carries it down a path and records it. Everything else, tunnels, proxies and rules, runs as plugins on top.
The Pitch in Four Numbers
- 17 of 17 ways out of the sealed sandbox tried, and all blocked, IPv6 included.
- 236 of 236 test functions passed, including end-to-end runs through a real WireGuard tunnel.
- 36 of 36 faults thrown at WireGuard tunnels handled, directly and through the rotate plugin.
- 11 of 11 forbidden requests sent to an exit with a valid token refused by the client’s policy.
How It Works
The kernel is small on purpose. It seals one program in, so the program can’t reach the network except through vpnw. For every connection it decides yes or no, picks a path and writes a record. Paths come in four kinds: direct, proxy, proxy over TLS and WireGuard. WireGuard tunnels work for one program at a time, without root.
Everything else is a plugin, running in a WebAssembly sandbox and using the plugin interface the way a program uses system calls. Observers watch. Advisors suggest. Guards enforce rules, including byte budgets where the kernel cuts a connection at the limit and records why. Tunnel plugins can rotate through a folder of WireGuard configs. Ledger seals each run’s record and spots altered lines, with checkpoints signed by a per-machine key that Ledger itself can’t read. Lab breaks the WireGuard path on purpose to prove the fixes work. And an Exit component gives fixed addresses with a second policy check at the far end, so even a valid token can’t push a forbidden request through.
It runs on Linux and macOS, with no root needed.
Who It’s For
- Teams running AI agents that should reach only the sites their task needs, with a record of every call.
- Scraping and data collection jobs that need controlled routes and rotation.
- Build and CI jobs where network access should be narrow and auditable.
- Developers who want to write network plugins in a sandbox with a clear interface.
Limits
The published results come from one two-CPU Linux machine plus a GitHub Actions runner, and the project doesn’t claim more than that. It’s Linux and macOS only for now. It’s a network layer for programs, not a consumer VPN app for browsing.
The Four-Question Screening
Every project featured here gets the same four questions, the way you’d screen a startup idea.
1. Where is the money in it?
The kernel is open source under Apache 2.0, with no paid tier. Network control for AI agents is becoming its own market, because security teams need to say what agents can reach and prove what they did. The paid paths are hosted exits with fixed addresses, a plugin marketplace with certified guards and tunnels, signed ledger storage for audits, and enterprise policy management across many machines. Proxy and scraping infrastructure is a second, established market that pays for reliable routes.
2. What real problem does it solve?
Programs with more network access than they need and no record of how they used it. An agent that can reach anything can be tricked into reaching anything. A job with no network record can’t be audited. VPN Works narrows the access and keeps the record.
3. The technology in plain words
Imagine giving each program its own phone line through a switchboard. The operator checks every number it dials against a list, connects only the allowed calls down the right line, and writes each call in a ledger that can’t be quietly edited. Extra services, like routing calls abroad or limiting minutes, plug into the switchboard without being able to rewire it.
4. Moat and differentiation
VPNs route whole machines. Firewalls block without much context. Proxy services rent addresses. VPN Works treats each program as its own sealed unit with a decided path and a signed record, and pushes everything else into sandboxed plugins. That’s a different shape from anything in the market, and it fits the agent era. The moat that can grow is the plugin ecosystem and the trust that comes from the escape-route and fault testing.
Why It Matters
As agents act on the open internet, “what could it reach and what did it do?” becomes a security question that needs a precise answer. A network layer built per program, with a record of every connection, answers it.
Follow the Project
Read about the platform and the plugins, try the demo, start with the quick start, see the roadmap, or get the code from the VPN Works repository on GitHub. VPN Works is listed with the other open-source projects on SoftDevStudio.com, and more featured projects are in the Projects section.