How YGOOW compares
We will not tell you YGOOW is the only secure messenger — that claim is how you spot marketing. Several excellent projects solve overlapping problems, and some are more mature than we are today. Here is an honest map of where YGOOW sits, and where it does not.
At a glance
| YGOOW | Signal | Session | Briar | |
|---|---|---|---|---|
| No phone number or email | ✓ | ✗ (phone) | ✓ | ✓ |
| No server-side account | ✓ | ✗ | ~ (key ID) | ✓ |
| Tor / onion transport built in | ✓ (your choice) | ✗ | ~ (own network) | ✓ (default) |
| Works offline over local mesh | ✗ | ✗ | ✗ | ✓ |
| Key can be any file or password | ✓ | ✗ | ✗ | ✗ |
| A different key per message | ✓ | ✗ | ✗ | ✗ |
| Quorum (K-of-N) unlock | ✓ | ✗ | ✗ | ✗ |
| Independent audit | planned | ✓ | ✓ | ✓ |
| Open source | planned | ✓ | ✓ | ✓ |
| Platforms | Android | all | all | Android + desktop |
✓ yes · ✗ no · ~ partial or qualified. Where we wrote planned, we mean exactly that — and we say so again in the whitepaper and our security policy.
What is genuinely different about YGOOW
No single row is the point — the combination is:
- No identity, anywhere. Not a phone number, not even a public-key “address” that lives on a server. Your keypair is generated on-device and shared only when you choose, in person.
- Your key is anything. A password, a file you both have, a link, a random key in a QR, or a Shamir split — hashed locally, never transmitted. No other messenger here lets the shared secret itself be an arbitrary artifact.
- A different key per message. The same room is text to one person and a lock to another, with no error and no hint — the property we pulled apart in “no oracle”.
- A deaf relay. The server stores only ciphertext and timestamps; seized, it is noise. (Briar drops the server entirely with peer-to-peer — a different answer to the same fear.)
- Quorum unlock. A message that only opens when K of N people combine their keys. One infiltrator with one share learns nothing.
Where the others are ahead — today
We would rather say this than have you discover it:
- Signal is the audited, reproducible-build, decade-hardened standard. Its Double Ratchet provides post-compromise security that YGOOW does not have yet, on every platform. For most people, most of the time, it is the right answer.
- Briar works with no internet at all — over Bluetooth and local WiFi — which is exactly what you want in a blackout or a protest, and it has been independently audited (Cure53).
- Session runs on a decentralized network with no central operator to seize, and ships on every platform today.
YGOOW is younger than all three. We have no independent audit yet, no post-compromise ratchet yet, and we are Android-only. Today YGOOW has forward secrecy; post-compromise security (a DH ratchet) is a roadmap item, not a present claim. None of this is buried — it is in the whitepaper and on our security page.
How to choose
- Want a battle-tested everyday messenger your less-technical contacts will also use? Signal.
- Need to communicate with no infrastructure at all, offline, in a crisis? Briar.
- Want no central operator and cross-platform reach today? Session.
- Want no identity on the server, a key that can be any secret you already share, per-message deniability, quorum unlock, and Tor by choice — on Android? That is the gap YGOOW was built for.
Your key, your rules — everything else is redacted.