Comparison

Helix vs Session

Session deserves respect: no phone number, decentralized routing, open source. It's one of the most privacy-serious messengers out there. Helix shares the philosophy and pushes it further — our own network instead of a shared one, post-quantum encryption, full forward secrecy, and a complete suite for people who are genuinely targeted.

 HelixSession
Identifier requiredNone — closed, invite-onlyNone — random account ID (good)
NetworkOur own onion networkShared decentralized service-node network
Onion-style routingYes — ours, multi-hopYes — via the shared network
Post-quantum encryptionYesNo
Forward secrecy / self-healingYes — continuously re-keyed ratchetLimited — protocol trades some of this for its model
Voice & videoYes, global, own transportVoice yes; video limited
Built-in VPNYes — our own, zero-logNo
Self-custody walletYesNo
Disposable mailYesNo
Plausible deniability / hidden appYesNo
Hardened device optionYes (GrapheneOS phone)No
Closed to strangersYesAnyone with your ID can message you

What Session gets right

Session threw out the phone number entirely — you get a random account ID — and routes messages over a decentralized network of service nodes rather than a single company's servers. That's a genuinely strong privacy posture, it's open source, and for people who want anonymous, no-account, decentralized chat, it's a serious option. We're fans of the direction.

Where Helix is the bigger system

Session is excellent anonymous, decentralized chat. Helix is the whole operational-security system — our network, post-quantum, and built for when you're the target.
Get HelixSee all features