Signal Protocol E2EE
Industry-standard double-ratchet encryption. Only you and your contacts hold the keys.
In active development. Contribute on GitHub or support on Patreon.
AWChat is a mobile-first messenger with X-Lite simplicity and messages that purge one day after everyone has seen them. The server relays ciphertext — it never reads your conversations.
Android is the official v1 target. Linux desktop and TUI clients are experimental.
Alex
Seen by all · purges in 24h
Features
AWChat combines proven cryptography with a retention model you can reason about — no vague “disappearing” toggles, no server-side snooping.
Industry-standard double-ratchet encryption. Only you and your contacts hold the keys.
Once every participant has read a message, a 24-hour countdown begins — then it's gone everywhere.
No clutter, no feeds, no algorithm. Just conversations with the people you choose.
The relay stores and forwards encrypted envelopes. Message bodies are never decrypted server-side.
Built with Jetpack Compose and Material 3 Expressive — fast, fluid, and designed for phones first.
Open development on GitHub with a 24-PR roadmap. We ship in public and welcome contributors.
How it works
Ephemeral doesn't mean instant. AWChat uses a clear, client-computed seen-by-all model so everyone knows exactly when data goes away.
Messages are sealed with libsignal before they leave your phone. Keys stay in SQLCipher-backed local storage.
The Elixir relay forwards encrypted envelopes to recipients. It verifies signatures — never plaintext.
When all participants have seen a message, clients coordinate a signed purge. One day later, it's deleted for good.
Get involved
AWChat is under active development — we're on PR 12 of 24 and moving quickly. Whether you write Kotlin, Elixir, Rust, or docs, there's room to contribute. Or back the project on Patreon and follow the build.
Fund development and get behind-the-scenes updates from awfixer.
patreon.com/awfixer