TrojanSecurity
Walls you can
inspect yourself.
Troy fell to a gift, not a siege. So we obsess over the gate: what gets in, what gets out, and what is left behind. Here is every layer, in the order an attacker would meet it.
The armour
Five layers between
you and the watchers.
AES-256-GCM and ChaCha20
State-grade ciphers over WireGuard, with perfect forward secrecy. Keys rotate hourly and never touch a disk.
Strict no log policy
No browsing history, no connection timestamps, no source IPs, no bandwidth per user. Verified by independent audit.
Kill switch and leak guard
If the tunnel falters the gates close. Traffic is blocked at the system level. DNS, IPv6 and WebRTC leaks sealed by default.
Stealth mode
Our namesake. Traffic is wrapped to look like ordinary HTTPS so deep packet inspection sees nothing but browsing.
Open source, openly audited
Apps and protocol are public. Professionals are paid to break them and reports are published in full.
Private DNS
Every query resolves on our own encrypted resolvers inside the tunnel. Nothing leaves in the clear.
The Trojan protocol
Hidden in
plain sight.
Most VPNs are easy to spot on the wire, which is why restrictive networks block them. Trojan wraps WireGuard inside a TLS session that is indistinguishable from a visit to any ordinary website. The censor sees traffic to a web server. Inside, your traffic moves.
Your real IP, the servers you connect to, timestamps, DNS queries, the sites you visit, and per-user bandwidth. We keep aggregate load per server, nothing tied to a person.
It powers off. Because it runs from RAM with no disk, the seizing party receives a blank machine. This has happened once, in 2024, and we published the outcome in the transparency report.
Yes. Every node in all 94 cities boots from a signed read-only image and mounts no persistent storage.
Trojan Privacy AG is incorporated in Zurich, Switzerland, outside the Five Eyes and Fourteen Eyes agreements and with no mandatory data retention law for VPNs.
All client apps and the protocol implementation are on GitHub under the GPL. Server orchestration is private for operational security but is in scope for every audit.
Threat model
Who we
defend against.
- AYour ISP and mobile carrierSees only a tunnel
- BPublic Wi-Fi operatorsSees encrypted noise
- CAdvertisers and trackersLose your real IP
- DCensors and DPI systemsSee ordinary HTTPS
- EUsNothing to hand over