Webmail for Stalwart Mail Server.
Bulwark puts mail, calendar, contacts and files in one browser client that talks JMAP to your own server, for a household, a small team or a whole organisation.


Bulwark at a glance
Open source
AGPL-3.0, developed in public on GitHub.
Built on JMAP
Stalwart pushes each change, and the client fetches only the difference.
32 languages
Including German, French and Spanish, and Arabic, Hebrew and Persian right to left.
Built in the EU
Written and maintained in the EU.
Pick the page for your setup.
Stalwart is the mail server. Bulwark is the client.
Stalwart stores your mail; Bulwark reads and writes it over JMAP and keeps no copy.
Setting up Stalwart| Stalwart does | Bulwark adds |
|---|---|
| Receives and sends mail, filters spam | Mail, calendar, contacts and files in one browser window |
| Stores mailboxes, calendars, address books and files | Search across all four, and push updates as they happen |
| Holds the accounts, groups and shared mailboxes | Policies, locks and signatures per domain or group |
| Can be your OpenID Connect provider | Sign-in through that provider or another one, and an admin console |
What the four apps do.
Set the rules once for every mailbox in a domain or group.
Lock a setting and users see “Set by your organisation” next to it. Each domain or group can get its own signature, templates and external mail label, and people sign in through your identity provider.
Bulwark for organisations

A shared mailbox the whole team can work from.
A group mailbox in Stalwart shows up under Shared for every member. Everyone reads, files and replies from the team's address, and Drafts and Sent stay with the group. Thunderbird and phone mail apps keep working next to it.
Bulwark for small businesses

Every account in the house in one window.
Sign in to your own mailbox and the family's at once and switch with one click.
Bulwark at home

Run it as a container, or as static files.
Bulwark runs as a Node.js container with an admin console. Bulwark Lite is the same client built as static files, for any web host or for Stalwart to serve itself. Lite leaves out the admin console, plugins, office editing and web push.
Compare the two Take the one-minute quiz| Feature | Bulwark | Bulwark Lite |
|---|---|---|
| Mail, calendar, contacts and files | Yes | Yes |
| Several accounts at once | Yes | Yes |
| Sign-in with a password and TOTP | Yes | Yes |
| Single sign-on (OAuth, OpenID Connect) | Yes | Only when Stalwart serves Lite |
| Policies, locks and organisation signatures | Yes | From a policy.json file |
| Admin console and setup wizard | Yes | No |
| Plugins, such as S/MIME | Yes | No |
| Settings that follow you between devices | Yes | No |
| Office document editing | Yes | No |
| Web push notifications | Yes | No |
| Runs on | Docker or Node.js, amd64 and arm64 | Any static web host, a small nginx container, or Stalwart |
Install Bulwark in three steps.
You need a Stalwart server, and Docker for the container or any web host for Lite.
- 1Run the container.
$ docker run -d --name bulwark -p 3000:3000 -v bulwark-data:/app/data ghcr.io/bulwarkmail/webmail:latest - 2Run
docker logs bulwarkand open the setup link it prints. The wizard checks your Stalwart server and sets the admin password. - 3Put your reverse proxy in front for HTTPS. The docs have examples for Caddy, nginx and Traefik.
- 1Download
bulwark-lite-<version>.zipfrom the latest release and unzip it. - 2Set
jmapServerUrlinconfig.jsonto your Stalwart server. - 3Upload the folder and turn on the Permissive CORS policy in Stalwart's HTTP settings. The static hosting page has the steps, and how to let Stalwart serve Lite itself instead.
More from the Bulwark project.
Bulwark is open source under AGPL-3.0.
The code, the issue tracker, the release notes and the security advisories are public. Usage stats are off by default; an admin can turn on an anonymous report. So far 6,638 instances have sent it at least once. That counts every install that ever reported, not the ones running today, and installs with the report off aren't counted at all. Sponsors pay for the work.
Questions about running Bulwark
Is Bulwark the mail server?
Bulwark is the client. Stalwart is the mail server: it holds the messages, speaks SMTP, and owns the accounts and the spam filtering. Install Stalwart first, then point Bulwark at it.
Who is Bulwark for?
Anyone who runs Stalwart: one person or a family at home, a small business with a shared mailbox, or an IT department with an identity provider and many domains. The pages for organisations, small businesses and homelab show what each one gets.
Why JMAP?
JMAP moves threading, search and change tracking to the server and returns only what changed. The inbox updates by push, and marking twenty messages as read is one request.
Bulwark or Bulwark Lite?
Choose Lite if you want static files and your users sign in with a password, or with Stalwart's own sign-in when Stalwart serves Lite. Choose Bulwark for single sign-on without Stalwart serving the client, plugins, settings sync, office editing or the admin console. Both build from the same code, and Stalwart keeps the mail either way, so you can switch later. Bulwark's admin settings and synced settings don't carry over to Lite.
Does it work with a Stalwart server I already run?
Yes, if it runs Stalwart 0.16.6 or newer. Stalwart 0.16 works with any current Bulwark; Stalwart 1.0 needs Bulwark 1.18.0 or newer. Point Bulwark at the JMAP endpoint and sign in with the accounts you have. Nothing migrates, and Stalwart stays the source of truth. Before a server moves to 1.0, read the upgrade guide.
What does it cost?
Nothing. Bulwark is open source under AGPL-3.0 and there is no paid edition. If you change the code and let people use your version over a network, the AGPL asks you to offer them your changed source; the SOURCE_CODE_URL setting points Settings > About at it. There is no paid support for Bulwark today. If your organisation would want it, tell us what you need: dev@bulwarkmail.org.
What does deployment look like?
One container next to Stalwart, behind the reverse proxy you already use, or Bulwark Lite as a folder on any web host. There are examples for Caddy, Traefik and nginx, a Compose file for Stalwart and Bulwark together, standalone builds on every release for installs without Docker, and the Lite zip.
How do security fixes reach me?
Fixes ship as new releases, and the project has published 14 GitHub security advisories for fixed vulnerabilities so far. Bulwark (not Lite) checks for a new release every hour and shows it on the login page and in the admin console. Every release file has a .sha256 file, and since 1.12.0 every image and download has a build attestation you can check with gh attestation verify (it needs a GitHub login). Security fixes and updates has the details.
Why does Lite need a CORS setting on the mail server?
In Lite the browser talks to Stalwart directly, from your web host's address, and browsers only allow that when the mail server says so. Turn on the Permissive CORS policy, under Settings > Network > HTTP > Security in Stalwart's web admin. When Stalwart serves Lite itself, the address is the same and nothing needs changing.
Is there a phone app?
Bulwark Mobile is a beta for Android and iOS: the Android app comes from GitHub releases, the iPhone app from TestFlight. In a phone's browser the webmail itself works too, and over HTTPS it installs as an app. Mobile apps and push has the links.
What does my server need?
Stalwart 0.16.6 or newer, or 1.0 with Bulwark 1.18.0 or newer, and for the container Docker on amd64 or arm64. On the project's test VM the container used about 70 MiB of memory at idle, signed out; Requirements has the method. Lite needs only a web host.
Can I try it first?
Yes. demo.bulwarkmail.org runs the client on sample data with no mail server behind it. Press Launch demo and click through mail, calendar, contacts and files; nothing is saved or sent, and a reload starts over.