Documentation

Three steps take you from a Stalwart server to a working inbox. The rest of the manual is reference: configuration, features, deployment and the extension API. If you are deciding whether Bulwark fits, start with the page written for organisations, small businesses or homelabs.

Start here

  1. 1
    Have Stalwart running. Stalwart is the mail server. The Stalwart setup page covers installing it first. Which versions work together:
    StalwartBulwark and Bulwark Lite
    0.16.5 or olderNot supported
    0.16.6 or a newer 0.16Any current release
    1.01.18.0 or newer
  2. 2
    Run the container. Docker is the only requirement. There is nothing to clone and no .env file to write first.
    docker run -d --name bulwark -p 3000:3000 \
      -v bulwark-data:/app/data \
      ghcr.io/bulwarkmail/webmail:latest
  3. 3
    Open the setup link. docker logs bulwark prints a link with a one-time setup token, valid for an hour. The setup wizard checks your JMAP server, chooses OAuth or password sign-in, generates a session secret and sets the admin password. The configuration and authentication pages cover each screen.

Bulwark Lite has no container and no wizard: download the zip from a release, set jmapServerUrl in config.json, upload the folder to any web host and allow CORS in Stalwart. The Lite guide has the details.

Choose how to install

When something doesn't work

Troubleshooting collects the problems people run into most: sign-in failures, an empty mailbox tree, sending limits, push, a setup wizard that comes back, and plugins that do nothing. The guides walk through the admin console, sign-in, plugins and the organisation settings step by step.