We started Peerlify because the existing private-networking tools all hit the same wall when serious operators tried to use them at scale. The wall was the same shape every time: not "the tunnels don't work" but "I cannot reason about who is on my network, and I cannot answer audit questions without grep."
This post is the founding statement: what we believe, what we're building, and what we're not.
What we believe
A private network should look like a control room, not a tunnel dashboard. The questions a security engineer asks at 3 AM ("who connected to prod-db in the last hour, from which devices, owned by which people?") should be answerable with one query and one screen. The questions an auditor asks at quarter end ("who held Admin in March, and what did they change?") should be answerable from the audit log without joining three systems.
That's the high bar. Most tools we've used in this space optimize for the first ten minutes — install, connect, see green. We're optimizing for month four.
What we're building
Peerlify is an identity-aware mesh VPN: devices connect to each other over end-to-end encrypted tunnels, directly when the network allows it and through a relay when it doesn't, and every device belongs to a person who signed in through an identity provider. Membership, devices, access rules and the audit log are all first-class. The console is built around the questions operators actually ask.
The shipping order: identity, then policy, then observability, then scale. We're not chasing feature parity with anyone. The bar is "would I trust this with my own organization" — and we'll only ship something when the answer is yes.
What we're not
We're not building a consumer VPN for hiding your browsing. We're not building a self-hosted product: we run the control plane and relays, you run the clients. We're not building a tunnel-only tool that punts policy to a different vendor.
We are building it in public, and we're going to write here as we go — engineering posts, design posts, the occasional honest note about what didn't work. The first batch is up, more on the way.
If you build, run, or audit private networks for a living, we'd love to hear from you.