Hushnet separates identity from activity across two independent hops. No single party holds enough to profile you — by architecture, not by promise.
Three constraints shape every decision.
Traffic is sealed for the exit before it reaches us. Seizure or subpoena yields no content.
Accounts are random numbers. No email, no name, no phone required to begin.
Connecting addresses are never stored. Payments are kept separate from usage.
| Open Wi-Fi | Typical app | Hushnet | |
|---|---|---|---|
| Sees destinations | Network + ISP | The provider | Neither hop alone |
| Links you to history | — | Email + billing | Random number only |
| On strict networks | Throttled | Often blocked | Resembles ordinary web traffic |
| Verification | — | Trust us | Check exit keys yourself |
You encrypt to the exit. We carry what we cannot open. The exit delivers without knowing whose it is.
Relays run by us. Exits run by independent partners with published keys. Both would need to collude — and still lack the link.
The app shows the exit public key under Location. Compare it to the partner directory. Open-source clients; reproducible builds in progress.
Blends with modern web traffic; retries with padding when filtered.
Datagram transport avoids tunnel-in-tunnel stalls.
Ads, trackers and malware domains blocked at the exit.
Shared slots without staff emails. 5 live connections.
Relays near you for speed; exits chosen for independence.
No data to monetize, so nothing to upsell.
5 live devices. Unlimited sign-ins.
Shared pool for field crews. No staff emails.
Card, Lightning, cash-by-mail. 30-day return. Students + nonprofits half price.
Account number and connecting address while connected. Never destinations or content; connecting addresses are not stored.
Most multihop runs both hops. Our exits are independent, so one operator alone cannot link you.
Usually. Traffic resembles ordinary web transport and is harder to fingerprint. Stealth padding helps further.
Five simultaneous. Sign in anywhere; only active connections count.
Yes via WireGuard configs. You keep split-trust, without stealth camouflage.
Lightning or cash-by-mail credited to your number. Card stays with the processor, not tied to usage.
“I filed from lobbies where the login tracked more than my deadline. I wanted something a fixer could use without an email — or a tutorial.”
— Maya, network engineer. Reachable at maya@hushnet.example. Fictional demo; no photo, no tracking.
A number, a connection, back to work. Two minutes.
30-day return · Open source · No email required