Skip to content

Self-hosting ​

Atlas runs on your own infrastructure and writes backups to an S3-compatible bucket you control, so the data never has to leave your network.

In this section ​

Set up a self-hosted deployment in this order:

StepPageWhat you do
1Storage setupPrepare redundant disks, run MinIO in Docker, secure it, and check the tenant bucket.
2Scheduling and bandwidthPlan bandwidth and run backups on a schedule with cron or systemd timers.
3Replica setupKeep a second copy in another location with provider replication or a copy tool.

Once the replica exists, Replicas covers restoring from it and verifying it.

Platform recommendation ​

Run Atlas in production on Linux: Ubuntu Server 22.04 or later, or Debian 12 or later. Atlas is designed and tested primarily there.

  • Docker volume drivers and bind mounts perform best on Linux. Docker Desktop on macOS and Windows adds a virtual machine between the container and the disk.
  • systemd timers and cron schedule backups without extra tooling.
  • File permissions, symlinks, and mount points behave predictably, and a dedicated server carries no desktop overhead.

Atlas also runs on macOS and Windows for development and testing. The guidance in this section assumes Linux.

System requirements ​

ResourceMinimumRecommended
Node.js22.12 or later (SDK: 22.8)Current LTS
RAM1 GB2 GB or more
CPU1 core2 cores or more
DiskDepends on mailbox sizesSee Storage setup
NetworkStable internet connectionDedicated uplink, see Scheduling and bandwidth

Atlas itself is lightweight. The data it moves is not: a tenant-wide backup of many large mailboxes can transfer tens or hundreds of gigabytes over HTTPS.