Stalwart adapts to the size of the deployment.
The same product runs the smallest single-node setup and the largest multi-region cluster, so what you start with does not limit what you can grow into.
Stalwart serves every mail and collaboration protocol your clients need (SMTP, IMAP, JMAP, POP3, ManageSieve, CalDAV, CardDAV, WebDAV) and stores data in the storage backends you already run. The same product scales from a single node to a multi-region cluster, with Stalwart Keep for coordination and short-lived state.
Stalwart adapts to the size of the deployment.
The same product runs the smallest single-node setup and the largest multi-region cluster, so what you start with does not limit what you can grow into.
one Stalwart process serves every protocol on a single server, suited to small organisations and evaluation deployments.
three or more nodes share a distributed data store; any node can serve any protocol, and listener allocation per node can be tuned for unified, service-specific or geographically distributed setups. See cluster overview.
Stalwart runs on Kubernetes, Apache Mesos and Docker Swarm; the orchestrator handles node lifecycle and scaling. See orchestration overview.
nodes split across data centres or regions, paired with a multi-region data store and geo-replicated blob storage; global load balancers or DNS-based routing direct traffic regionally.
Stalwart was engineered to scale from the start, paired with modern storage backends like FoundationDB.
Capacity grows by adding nodes, and high availability comes from the design itself, not from external proxies. Any node can take over for any other, so a node failure never strands a user or a queued message.
Stalwart separates persistent state into four roles and lets you pick a backend for each, so you can match what the team already runs (or already knows how to back up) instead of being told which database to deploy.
Full-text search can run inside Stalwart or be delegated to a dedicated engine.
The internal engine indexes 17 languages and requires no extra service, which is the right fit for small and medium deployments. For larger workloads, a dedicated engine takes the indexing load off the data store. Whichever engine is used, the text inside PDF, Office, OpenDocument, EPUB and RTF documents is extracted and indexed, both for mail attachments and for files in file storage.
per-mailbox encryption with S/MIME or OpenPGP, including post-quantum ML-KEM keys; the server holds only public keys. See encryption at rest.
outgoing mail encrypted for each remote recipient whose key is discovered or harvested. See encryption gateway.
messages and files encrypted with server-held AES-256-GCM or ChaCha20-Poly1305 keys before they reach the blob store, so an S3 or Azure provider holds only ciphertext; keys rotate without downtime. See blob encryption.
passkeys for passwordless, phishing-resistant sign-in, two-factor authentication, and app passwords and API keys with their own IP restrictions and expiry. See passkeys.
ACME, DANE, MTA-STS and TLS reporting.
rate limiting, automated banning, ASN and GeoIP blocking, ACLs and per-account IP restrictions.
the server is written in Rust. The codebase has been independently security-audited; the report is published in the Stalwart blog.