When privacy, censorship resistance, and decentralization matter, the usual mainstream messengers won’t cut it. Instead, a number of privacy-first, often federated or decentralized instant messaging apps have emerged. Below is a comparison of the most relevant ones.
| Messenger | Year | Architecture | Encryption | Federation/Decentralization | Self-Hostable | Unique Traits | Platforms |
|---|---|---|---|---|---|---|---|
| SimpleX | 2021 | Decentralized (relay-based) | Signal (modified) | ✅ Full decentralization | ✅ | No IDs, no metadata, no contact list | Android, iOS, desktop |
| XMPP (Conversations) | 1999 / 2014 | Federated (XMPP protocol) | OMEMO | ✅ Federated | ✅ | Mature, modular, server-agnostic | Android, iOS, desktop |
| Delta Chat | 2017 | Email-based | OpenPGP | ✅ Via email infrastructure | ✅ (email) | Uses existing email accounts | Android, iOS, desktop |
| Matrix (Element) | 2014 / 2016 | Federated | Olm/Megolm | ✅ Federated | ✅ | Bridging to Slack/Telegram/IRC etc. | Android, iOS, desktop |
| Session | 2020 | Decentralized (blockchain) | Signal (fork) | ✅ Blockchain node-based | ⚠️ Only with staking | Fully anonymous, no phone/email | Android, iOS, desktop |
I would like to add :
Network protection layer: Next DNS / nym Mixnet for both financial and personal use.
Mobile protection layer: GrapheneOS only for specific devices.
Desktop protection layer: Qubes OS has some hardware support limitations.
CEO said:I would like to add :
Network protection layer: Next DNS / nym Mixnet for both financial and personal use.
Mobile protection layer: GrapheneOS only for specific devices.
Desktop protection layer: Qubes OS has some hardware support limitations.
better to discuss these in dedicated threads
JohnnyDoe said:better to discuss these in dedicated threads
I mentioned it here because of the complex sophisticated relationship.
edited 8 Dec 2025#6
GuaraniGhost said:I read that GrapheneOS will lose access to immediate updates to changes announced by Google when Android 16 is released.
They will find a way to fix it.
grapheneos.org/faq#future-devices
I like ElementX (Matrix), nice UI
Session is in trouble:
x.com/session_app/status/2034446033732968901#m
Session in trouble again.
What about Threema? Since many many years one of my preferred platforms, next to signal with a random number + session
I don’t think session will close
Here's a good article on why Signal sucks if you're running extra-curricular activities on the side (SimpleX is better): https://bible.beginnerprivacy.com/opsec/signalnoanonymity/
Given Session's problems, I'm looking elsewhere but to my horror, SimpleX doesn't encrypt calls. WHAT! That's a serious shortcoming.
If Signal switches to usernames and no phone number required, that will be enough for me if Session folds.
elementX seems the best alternative so Session
WhoMe said:Given Session's problems, I'm looking elsewhere but to my horror, SimpleX doesn't encrypt calls. WHAT! That's a serious shortcoming.
If Signal switches to usernames and no phone number required, that will be enough for me if Session folds.
I should probably clarify what I said about SimpleX not encrypting calls. It only does it for compatible phones. Someone I called has an older model Galaxy and his phone is "too old" to encrypt the call. Signal, Session, even WhatsApp can encrypt the call regardless of the model of phone. So that's something SimpleX must fix.
WhoMe said:I should probably clarify what I said about SimpleX not encrypting calls. It only does it for compatible phones. Someone I called has an older model Galaxy and his phone is "too old" to encrypt the call. Signal, Session, even WhatsApp can encrypt the call regardless of the model of phone. So that's something SimpleX must fix.
GraphenOS response is good enough :
Why are older devices no longer supported?
GrapheneOS aims to provide reasonably private and secure devices. It cannot do that once device support code like firmware, kernel and vendor code is no longer actively maintained. Even if the community was prepared to take over maintenance of the open source code and to replace the rest, firmware would present a major issue, and the community has never been active or interested enough in device support to consider attempting this. Unlike many other platforms, GrapheneOS has a much higher minimum standard than simply having devices fully functional, as they also need to provide the expected level of security. It would start to become realistic to provide substantially longer device support once GrapheneOS controls the hardware and firmware via custom hardware manufactured for it. Until then, the lifetime of devices will remain based on manufacturer support. It's also important to keep in mind that phone vendors claiming to provide longer support often aren't actually doing it and some never even ship firmware updates when the hardware is still supported by the vendors...
grapheneos.org/faq#legacy-devices
-
Tech Spec:
WebRTC uses two pre-existing protocols, Datagram Transport Layer Security (DTLS) and the Secure Real-time Transport Protocol (SRTP).
Ref. Securing
SimpleX Chat allows you to make end-to-end encrypted audio and video calls with your contacts via WebRTC. Note: Group calls are not supported at this time.
Ref. Audio & video Calls
SRTP in WebRTC
Ref. SRTP in WebRTC
WebRTC. All of the WebRTC related protocols are required to encrypt their communications using DTLS; this includes SCTP, SRTP, and STUN.
Ref. DTLS (Datagram Transport Layer Security) - Glossary | MDN
Vizier · 7 replies · last 13 Nov 2026
Virtualine · 8 replies · last 2 Nov 2026
Laid Back Llama · 4 replies · last 30 Oct 2026
Vizier · 0 replies · last 24 Oct 2026
True power moves in silence.
