Get the app
Several ways to run Sublemonable — mobile, desktop, or the browser. And, if you count running the entire thing yourself, one more — which we encourage.
iOS and Android
The mobile apps aren't in the stores yet. The badges below will light up when they are — segments and all.
Browser — no install needed
The web app is a full client: keys generated and stored in your browser, messages encrypted before they leave it. It's also an installable PWA — open it, and your browser will offer to add it to your home screen or dock (look for “Install app” in the address bar on desktop, or Share → Add to Home Screen on mobile). Installed, it works offline for composing: outbound messages queue locally and send when you reconnect. Only the UI is cached — never your messages.
Linux — .deb, .AppImage, .rpm
A native desktop app built with Tauri — no bundled Chromium, just a small Rust backend. The .deb is the primary package for Debian, Ubuntu, Kali Linux, Parrot OS, and Pop!_OS. The .AppImage is universal — it runs on any distro without installing. An .rpm is also produced for Fedora and RHEL (community-supported).
Screenshot protection on the desktop app is a focus-loss blur overlay — the same mechanism as the browser. It's best-effort: Linux has no universal way to hard-block screen capture on Wayland or X11. For an OS-level hard block on message content, the Android app is the platform that provides it.
Self-host it
Don't want to trust our server? Good instinct. Run your own — it's a Go binary, a Postgres database, and a Docker Compose file:
git clone https://github.com/jackofall1232/sublemonable.git
cd sublemonable
cp .env.example .env # set DATABASE_URL, JWT key paths, TLS paths
docker compose up -d # server + postgres
# optional Tor hidden service:
docker compose -f docker-compose.yml -f docker-compose.tor.yml up -dFull instructions — TLS setup, environment variables, the optional Tor hidden service, backups — are in the self-hosting guide.