Keep plaintext on the client
Anomonus is built around local encryption before upload, not around server-side trust claims after the fact.
About Anomonus
A secure messaging app built for encrypted secret sharing, QR flows, and controlled access.
Anomonus is not presented in the code as a generic chat network. It is a focused product for creating, sharing, opening, and optionally burning encrypted secrets through mobile-first encryption and viewer-first browser access.
Mission
Anomonus is built around a zero-knowledge style client model. The mobile app encrypts supported secret payloads locally, while the backend stores ciphertext, metadata, tickets, and challenge state needed to serve those secrets back to authorized recipients.
From the current codebase, the product supports secret messages, links, locations, posts, and parties, along with QR opening, deep-link handling, PNG steganography, RSVP flows, and browser-based secret reveal through chat.anomonus.com.
Operating principles
How the current product is actually engineered.
Use native capabilities where they matter
Identity signing, device-binding keys, biometrics, secure storage, and Tor transport all rely on native platform surfaces in the current app.
Support more than one access path
The product includes QR, deep-link, browser viewer, and PNG steganography workflows because private sharing is rarely one-size-fits-all.
Product layers
The three layers that define Anomonus today.
Build the mobile secret client
The strongest current implementation lives in the mobile app: secret creation, local encryption, identity, secure storage, and open/share flows.
Expose a browser viewer
chat.anomonus.com exists as a public landing surface and viewer flow so recipients can open supported secrets in the browser with local decrypt.
Harden transport and device controls
The current code adds device binding, certificate pinning, Tor routing, privacy overlays, biometrics, and wipe-audit behavior on top of the secret model.