| Sign-up & identifiers | None — no phone number, no email, no account. Identity is a cryptographic key held on your device; there is no public ID string. | None — no phone number or email. Identity is a randomly generated Session ID, a persistent public string you share with contacts. Both approaches are strong; call this row a tie. |
| Browser / no-install use | Yes — persistent, full-featured client at app.sendant.io. Open a link, start messaging. Works on iPhone right now, in the browser. | No. Session ships native apps only; there is no web or browser client. |
| Native apps | Android app. No native iOS app yet — iPhone users use the browser client. | Native apps for iOS, Android, and desktop. |
| Network metadata & IP protection | Servers see only ciphertext content, and there is no phone number or email to leak — but Sendant does not onion-route, so it does not match Session's network-level IP protection. | Messages are onion-routed through a decentralized network of community-run service nodes, so no single node sees both your IP and your destination. The stronger design against network-level observers. |
| Encryption & forward secrecy | X3DH + Double Ratchet — the same cryptographic primitives Signal uses — with per-message forward secrecy, in the app and in the browser. | Custom Session Protocol. In moving off the Signal Protocol, Session dropped per-message perfect forward secrecy — a documented design tradeoff. |
| Independent audits | Not yet audited. An independent audit is planned; known limitations are documented rather than hidden. | Session's apps were audited by Quarkslab in 2021. The audit predates years of changes since, but it exists — a modest, real edge. |
| Bad-network behavior | Built for throttled, restricted, or intermittent networks: messages wait in an encrypted store-and-forward mailbox and deliver when your contact reconnects. Peer-to-peer and relay delivery paths are on the roadmap. | Depends on reaching the service-node network; nodes store encrypted messages for offline recipients. |
| Team & resourcing | Funded by optional paid tiers and actively developed. | Session laid off its entire paid team in April 2026 and now runs on a small donation-funded team after the community stepped in. Development continues, at a smaller scale. |
| Price, funding & tokens | Free. Funded by optional paid tiers — no ads, no token, no data monetization. | Free to use. The service-node network has historically been tied to a blockchain token, with operators staking to run nodes. |