New in 0.8.0: Tunnel plugins, rotating through WireGuard configs

The VPN, rebuilt as an operating system

One small core does what a kernel does for a network path. Tunnels, proxies and rules run on it, and so does everything you build. The OS is VPN Works; its kernel is vpnw.

Quick start How the OS is built
VPN Works as an operating system: programs on top, each with a network of its own; plugins as apps (Observer, Advisor, Guard, Tunnel); the plugin interface as system calls; the vpnw core as the kernel (seal, decide, carry, record); paths as drivers (direct, proxy, proxy over TLS, WireGuard); Linux or macOS as the host

17 of 17

Ways out of the sealed sandbox tried, and all blocked, IPv6 included

236 of 236

Test functions passed, with end-to-end runs of the real binary through a real WireGuard tunnel

36 of 36

Faults thrown at WireGuard tunnels and handled, run directly and through the rotate plugin: a silent peer, lost handshakes, an impostor, a DNS server that lies

11 of 11

Forbidden requests sent straight to an exit with a valid token, and all refused there by the client's own policy

Measured on VPN Works 0.8.0 by tools/record-results.sh in the code repository: the sandbox on a GitHub Actions Linux runner, the rest on one Linux machine with 2 CPUs.

Articles and case studies

All posts →

Get in touch

Teams running AI agents, scrapers or build jobs that need narrow, recorded network access, and anyone who'd like to write a plugin for VPN Works, are welcome to write.

Contact