Most messengers start by asking for your phone number. WhatsApp and Signal both do. WhatsApp encrypts message content by default, but it belongs to Meta, and Meta keeps the account metadata — who you talk to and when, plus device details. Signal also requires a phone number, even though it collects very little metadata and its protocol is treated as the reference standard in the field. If your goal is a messenger that never sees a phone number at all, the list of serious options gets short fast. Session is the most established one. MurMur is a much younger open-source project that takes a different route. This article compares the two honestly — including the places where Session is simply the better recommendation today.
| Session | MurMur | |
|---|---|---|
| Registration | None. A random session ID is generated on your device. | None. Your identity is a cryptographic key (npub) generated on your device. |
| E2EE by default | Yes | Yes — for messages and calls |
| Calls | Voice calls between users | E2EE calls, running in the browser |
| Metadata story | Messages travel through an onion network of independently operated nodes; nothing is tied to a phone number. | A single Rust relay in Europe that cannot read plaintext and keeps encrypted messages only for a limited time. |
| Install | Native apps from app stores, APK, desktop apps | PWA installed from the browser, no app store needed |
| Who runs it | The Session Foundation plus a community-operated node network | One open-source relay in Europe, run by the project itself |
This should be stated plainly. Session has existed for years, its code has been independently audited, it has a large user community, and its apps went through long real-world testing. If you want a no-phone-number messenger that many people already use, with mature native apps, Session is the safer recommendation right now. That is not a caveat — it is the honest answer for most people reading this. A young project with no security audit cannot compete with that track record, and pretending otherwise would be misleading.
No. Session generates a random session ID on your device during setup, and nothing connects that ID to a phone number or an email address.
There is no honest way to claim that. Both encrypt messages end-to-end and both are open source, but Session has been through independent audits and MurMur has not. Until an audit happens, treat MurMur as promising but unverified.
Yes. MurMur is a PWA: open the site in the browser on iPhone or Android and install it from there. No app store account is involved.
The account is lost. The cryptographic key is the identity, and there is no SMS recovery to fall back on. Backing the key up is on you.
Session routes messages through an onion network of community-run nodes, with content encrypted end to end. MurMur's relay cannot read plaintext either — it stores messages only in encrypted form, and only for a limited time.
If the browser-based approach sounds interesting, MurMur installs in a couple of minutes from murmurchat.org and works on both iPhone and Android. The source code is on GitHub. Just keep your key safe — there is no reset.