VERTEX

Vertex

Where paths meet.

A privacy-focused VPN built around a relay-vertex topology. End-to-end encrypted and transport-resilient.

client → vertex → exit

Designed around indirection

Six guarantees that follow naturally from the relay-vertex topology — not features bolted on after the fact.

End-to-end encrypted

X25519 Diffie-Hellman handshake derives a session key per device. Packets are sealed with ChaCha20-Poly1305 before they ever leave your device — the relay vertex only ever sees ciphertext.
Multi-vertex fan-out

Several independent relay vertices, exit servers connected to all of them, automatic client failover in roughly 100 ms. A single vertex outage is invisible.
Auto exit-select

Clients probe each relay vertex and read exit load on every connect, then pick the shortest path. Manual override is one tap away.
Device identity (TOFU)

A leaked password isn't enough. The exit pins your device on first use; an attacker also needs the identity key file from your machine.
Split routing

On-device CIDR table sends Russian destinations direct, the rest through the tunnel. 8 585 subnets, updated with each release.
Censorship-resistant transport

On the wire Vertex looks like ordinary encrypted web traffic — keeps working where conventional VPN protocols are filtered.

A vertex is the meeting point. Your client and the exit talk through it; the vertex itself only relays opaque ciphertext.

01
Install

Native apps for iOS, macOS, Android and Windows. Linux desktop and gateway builds available on request.
02
Authenticate

First launch generates an X25519 identity key locally. The exit registers it on first use.
03
Connect

Toggle the switch. The client picks the best vertex and exit, hands off seamlessly when the network changes.

Native, minimal, no telemetry.

Vertex is built around a single design principle: the network can't see your traffic, and we don't want to either.