# Deployment

Source: https://bulwarkmail.org/docs/deployment

Ways to run Bulwark on your own servers: static files, Docker and Compose, Stalwart's application install, Kubernetes or a manual install, and how to update each one.

- [Requirements and sizing](https://bulwarkmail.org/docs/deployment/requirements.md): What Bulwark and Bulwark Lite need to run, which architectures are built, and how much memory they used in a measured setup.
- [Static hosting](https://bulwarkmail.org/docs/deployment/static.md): Build inputs, config.json, the CORS setting on Stalwart, and host snippets for Bulwark Lite. (Bulwark Lite only)
- [Docker deployment](https://bulwarkmail.org/docs/deployment/docker.md): Deploy Bulwark with Docker and Docker Compose. (Bulwark only, not Lite)
  - [Docker Compose](https://bulwarkmail.org/docs/deployment/docker/compose.md): Run Bulwark alongside Stalwart with Docker Compose. (Bulwark only, not Lite)
  - [Reverse proxy](https://bulwarkmail.org/docs/deployment/docker/reverse-proxy.md): Set up a reverse proxy in front of Bulwark. (Bulwark only, not Lite)
- [Run Bulwark at home](https://bulwarkmail.org/docs/deployment/home-server.md): Stalwart and Bulwark on a home server, NAS or ARM board: Compose, a reverse proxy, bind mounts, Lite on an existing web server, and packages other people maintain.
- [Running several instances](https://bulwarkmail.org/docs/deployment/multi-instance.md): Run Bulwark as several replicas behind one load balancer, with a shared Redis-protocol store. (Bulwark only, not Lite)
- [Install on Stalwart](https://bulwarkmail.org/docs/deployment/stalwart-app.md): Let Stalwart host Bulwark Lite itself as a web Application, on the same origin, with no web server and no CORS. (Bulwark Lite only)
- [Kubernetes](https://bulwarkmail.org/docs/deployment/kubernetes.md): Run Bulwark on Kubernetes with the project's manifests (one or many replicas) or the community HelmForge chart. (Bulwark only, not Lite)
- [Manual deployment](https://bulwarkmail.org/docs/deployment/manual.md): Deploy Bulwark manually on a server. (Bulwark only, not Lite)
- [Running Bulwark for customers](https://bulwarkmail.org/docs/deployment/hosting-providers.md): One Bulwark for many customer domains: servers picked by domain, branding per web address, opening a mailbox from your panel, embedding, and several replicas. (Bulwark only, not Lite)
- [Monitoring](https://bulwarkmail.org/docs/deployment/monitoring.md): Send errors to your own error tracker, scrape Prometheus metrics, wire up health checks and export OpenTelemetry traces. (Bulwark only, not Lite)
- [Security fixes and updates](https://bulwarkmail.org/docs/deployment/security-updates.md): Where fixes are announced, how Bulwark tells you about a new release, and how to verify a download or image.
- [Updating](https://bulwarkmail.org/docs/deployment/updating.md): Release channels, how to upgrade each install type, and how the update notice works.
  - [Upgrading to Stalwart 1.0](https://bulwarkmail.org/docs/deployment/updating/stalwart-1-0.md): What to do on the Bulwark side when a server moves to Stalwart 1.0, and which server settings to check.
