VPN9 / PRIVACY AS ARCHITECTURE / LAUNCHING SOON

When we launch, we won't know who you are.

VPN9 is the only VPN whose architecture makes surveillance technically impossible. No email. No metadata. No cross‑server correlation. Not because we delete the logs — because the system never produces them. Every line is open source. Every server will be attestable. Be the first to know when we ship.

Put me on the list Read the source

※ No email required at launch · Pay with Bitcoin or Monero · AGPLv3

◐ §01 / 04 · The negative space Scroll to read
§01  /  The nine unknowns

Most VPNs say trust us.
We're building a system that can't betray you.

  • 01 Your IP address. — NEVER STORED
  • 02 When you connect. — NOT OBSERVED
  • 03 When you disconnect. — NOT OBSERVED
  • 04 Which relay you choose. — OUTSIDE OUR VIEW
  • 05 How much data you send. — UNMEASURED
  • 06 What sites you visit. — ENCRYPTED
  • 07 What apps you run. — OPAQUE
  • 08 Who you are in real life. — UNLINKABLE
  • 09 That any single account exists. — UNCORRELATED

True privacy isn't about trusting us. It's about building a system where trust isn't required — and then publishing the blueprints so anyone can check the math.

◐ §02 / 04 · How it's actually built ↓
§02  /  Architecture

Privacy by shape,
not by policy.

STEP 01 · ACCOUNT

A 7‑word passphrase. Nothing else.

No email, no phone, no identity document. Your passphrase is hashed with Argon2id and stored as bytes — never as anything we could link back to you. Add a password if you want. Or don't. 

> signup()
  → passphrase  = seven_words()
  → digest      = argon2id(passphrase)
  → stored      = { digest, ∅, ∅ }
  ✓ no email. no phone. no name.
STEP 02 · TOKENS

A token that describes the right, not you.

We issue a stateless JWT with a 24‑hour expiry. It carries the minimum a relay needs — and nothing more. Relays verify signatures locally. They don't call home. They don't tell us anything. 

> jwt.claims
  sub   : subscription_id
  exp   : +24h
  iat   : now()
  ~ ip, name, email, device : absent
  → verified locally at relay
STEP 03 · RELAY

The relay forgets you the instant you leave.

WireGuard in RAM only. No connection log, no bandwidth meter, no per‑session record. Disconnect and the tunnel is gone. The relay doesn't report session data anywhere — not even to us. 

> wg up
  peer  : client_pubkey
  ram   : session_handle
  disk  : —
  api   : no callbacks home
  ✓ forgotten on disconnect
◐ §03 / 04 · Build progress ↓
§03  /  Progress

Not a landing page pretending
to be a company.

BUILD MATRIX · LIVE last refresh  2026-05-22 17:53 UTC
01 Open-source code AGPLv3 · github.com/vpn9labs LIVE
02 Anonymous accounts 7-word passphrase · Argon2id READY
03 Bitcoin payments via Bitcart · non-custodial READY
04 Monero payments via Bitcart · non-custodial READY
05 WireGuard relay network RAM-only tunnels · no disk writes PILOT
06 Runtime attestation signed image digest · SBOM READY
07 Desktop client macOS · Linux · Windows BETA
08 Mobile client iOS · Android WIP
09 Independent audit scope signed with auditor UPCOMING
>  want to verify? read every line at github.com/vpn9labs  ·  a runtime attestation endpoint will serve /api/v1/attestation at launch so you can match the running digest against the signed build.
verify // preview · what you'll be able to verify at launch $curl https://vpn9.com/api/v1/attestation
{   "build_version": "v1.0.0-rc.x",   "build_commit": "<git sha>",   "image_digest": "sha256:…",   "sbom": "https://vpn9.com/sbom/…json",   "signature": "cosign://verifiable",   "logs_retained": 0,   "data_retained": "none" }
// every running image identified by signed digest. // the digest matches a reproducible build you can rebuild yourself. // the build matches source you can already read today.
◐ §04 / 04 · Try it yourself ↓
※  /  Diagnostic

Is your current VPN leaking?

Check Your Privacy

DNS Leak Test

Find out if your VPN is actually protecting your DNS queries from being exposed to your ISP.

Test Your DNS Security

Click below to check if your DNS queries are leaking to your ISP. This test works whether you're using a VPN or not.

What is a DNS leak?

A DNS leak occurs when your device sends DNS queries to your ISP's DNS servers instead of your VPN's secure DNS servers. This can reveal which websites you visit, even when your traffic is encrypted through a VPN tunnel. A proper VPN should route all DNS queries through its own secure servers to maintain your privacy.

The best privacy is the kind you never have to trust.

We're almost ready. Drop your address — you'll hear from us once, on launch day, and never again unless you want to. No marketing. No drip. No sale.

Put me on the list Read the source