-
Notifications
You must be signed in to change notification settings - Fork 0
Gatepath Network Overview
A privacy-focused VPN infrastructure
built around explicit routing and clear trust boundaries.
WireGuard transport with optional Tor integration.
Gatepath provides encrypted network transport using WireGuard, with optional and explicit Tor usage for users who need it.
Traffic behavior is never inferred, modified, or redirected automatically. Users decide how their traffic is routed.
Gatepath provides multiple distinct network paths. Each path represents a different routing intent.
A conventional WireGuard VPN path with clearnet egress.
Designed for encrypted transport without Tor.
An optional Tor SOCKS gateway available over the VPN.
Applications must explicitly opt in by using SOCKS. Traffic is not transparently routed through Tor.
Dedicated VPN paths that route traffic exclusively through Tor.
No clearnet fallback is provided. If Tor is unavailable, traffic fails closed.
Gatepath treats traffic intent as explicit.
- Standard VPN paths imply clearnet intent
- Tor SOCKS usage implies explicit Tor intent
- Tor-only paths imply exclusive Tor intent
Traffic is never reclassified or redirected automatically.
- Encrypted transport over untrusted networks
- Explicit Tor usage without transparent proxying
- Reducing accidental clearnet exposure on Tor-only paths
- Automatic anonymity
- Protection against browser fingerprinting
- Identity or account unlinkability
- Endpoint or device security
- Explicit opt-in over convenience
- No transparent proxying
- Separation of Tor and non-Tor paths
- Fail closed where Tor-only routing is intended
- Minimal assumptions about user behavior
Design decisions and threat models are publicly documented.
Operational details and infrastructure specifics are intentionally not disclosed.
Gatepath is under active development.
Some components, including Tor-enabled paths, are being rolled out gradually.
Documentation · GitHub · Wiki
No tracking. No analytics.