KeenVPN
A VPN is easy to describe and surprisingly hard to make behave consistently. KeenVPN is private networking across real devices, real stores, and a distributed set of exits.
- Engineering across clients, networking, and the systems that keep exits coherent.
- Shipped on Apple platforms and Google Play, with Windows and browser surfaces in the same product family.
What it is
KeenVPN is a privacy-focused networking product people actually install: apps on phones and computers, plus a browser extension for narrower proxy use. The promise is ordinary. Private networking that works.
The cost of that promise is everything around the tunnel.
The problem
A VPN demo on one machine is not a product. A product needs clients that speak each operating system correctly, a way to issue access without turning every connection into an identity log, exits in more than one place, and enough operational discipline to grow without inventing a new snowflake each time.
If billing identity and tunnel access collapse into the same trail, privacy becomes marketing language. If exits are chosen without regard to health, users land on bad networks. If each platform tells a different story, the product stops feeling like one product.
How we approached it
KeenVPN spans native Apple networking, Windows networking, Android, and browser-based proxying. The same product had to behave consistently across very different client environments.
The tunnels use WireGuard. Around that sits a control plane for accounts and configuration, and a set of exits that report their health so clients can be steered toward working capacity.
Privacy is treated as structure, not as a disclaimer. Payment and account concerns are separated from the credentials used to join a tunnel, so exits do not need to know who paid in order to accept a connection.
Client
Phone, computer, or browser
Account
Subscription and identity stay on the product side
Access
Tunnel credentials issued without collapsing those worlds
Exit
A healthy location accepts the session
Connection
Private networking for the user’s traffic
The parts that matter
Users want one product everywhere. Each platform has different background rules, networking APIs, and store constraints. Matching behaviour takes more work than matching screenshots.
A browser extension can be useful and narrower. It should not be sold as the same thing as a device-wide tunnel.
More locations help latency and choice. Every exit is another place that can fail, drift, or need attention.
Kill switches, split tunnelling, health-aware selection, and testing matter more than a feature checklist once people depend on the connection.
What I work on
My work sits across client networking, control-plane behaviour, and the infrastructure that keeps exits coherent. I do not publish a percentage claim. The evidence is the shipped clients and the systems underneath them.
Where it is now
KeenVPN is shipped software with ongoing platform and infrastructure work. The interesting problems remain the same: reliability on real networks, privacy that survives contact with billing, and honesty about what each client can and cannot do.