Skip to main content
Web (in the browser), desktop for Windows, macOS and Linux, and native apps for iOS and Android. One account works across all of them, and calls ring natively on your phone.
Yes. Messages, files and calls are sealed on the sender’s device and opened only on the recipients’. The server — even one you run yourself — only ever handles ciphertext. You can verify a contact with their safety number.
Not your content. The control plane brokers identity, push and licensing, so it sees sign-in and delivery metadata and which plan an organization is on — never message text or call media. See Accounts & privacy.
Encryption hides what you say, not that a conversation happens: your node can see the “envelope” — who’s talking to whom and when — which is inherent to delivering messages (and on a self-hosted node, it’s your own server). Bastion narrows the rest: message sizes are padded, notifications are generic by default, there’s no link-preview or contact-sync leak, and an admin can enable metadata-minimal mode to switch off typing and receipts too. See Accounts & privacy.
No. You can run your own node, or use the managed option — the same stack, operated for you, one organization per instance. See Pricing.
Flat per server, not per seat — unlimited members. Self-hosted is 99/month,managedfrom99/month, managed from 249/month, optional modules +$29/month each, and annual billing saves two months. There is no free tier.
The base module is chat and calls. Bastion is modular, so more capabilities can be enabled over time. On the roadmap: an independent review of the cryptography, broader data-subject tooling (export/erase) and the first optional modules.
Your key lives on your device and can be backed up with a passphrase. If you lose both the passphrase and every signed-in device, that key can’t be recovered — the server never had it. Keep your backup safe.