Features
Designed so there is little to hand over
VersoVPN is in development. Below is what we are building and how we intend it to work — stated as intent, because that is what it is today.
Privacy
Less data, not better promises
A no-logs policy is a sentence. What matters is whether the system could produce a log if someone insisted.
No account to identify
Access is tied to a subscription, not to a profile about you. There is no name field because there is nothing that would use it.
Payment separated from usage
Payment and usage are meant to stay apart. Settling in VVPN means there would be no bank record tying a person to a subscription in the first place.
Keep less, not promise more
The design target is that there is very little about a user to keep. If the service ships, exactly what is retained — and why — would be published then, rather than promised now.
Network
Capacity from operators, not from one datacenter contract
Operator-run capacity
Anyone can run a node and be paid for the traffic they serve. Coverage grows where people actually connect from.
Modern transport
WireGuard-based tunnelling: fast to connect, easy to audit, undramatic on battery.
Routing you control
Choose where you exit. Split tunnelling for the apps that break when they see a foreign address.
Clients
Boring on purpose
One tap to connect
The whole interface is a switch and a location. Everything else belongs in settings, not on the first screen.
Your devices, one plan
A subscription covers the devices you use, rather than charging per install.
Open where it matters
Any client we ship would come with public source and protocol details — a privacy claim nobody can inspect is a slogan.
No clients exist yet. Any that ship would be listed here once they work — naming platforms in advance is a promise, and we are not making one.
Get early access
The project is early and nothing is built yet. Leave an address and, if early access happens, you hear about it before it is announced anywhere else.
Write to [email protected] and we will add you.