Self-host Install
AliasVault is self-hosted with Docker. There are two ways to install it — pick based on how much you want managed for you versus how much you want to fit into infrastructure you already run.
Install Script Recommended
A fully managed setup. One script spins up every container, gets HTTPS for you, and gives you CLI helpers for updates and maintenance.
- Automatic HTTPS via Let's Encrypt
- Guided updates & migrations
- Production-ready defaults
Best for: a fresh VM or VPS dedicated to AliasVault.
A single all-in-one container you drop into your existing Docker stack. You bring your own reverse proxy and TLS, and keep full control.
- Fits Portainer, Unraid, Synology & other homelab tools
- Bring your own TLS (Traefik, Nginx, HAProxy, Caddy…)
- Updates via
docker pull(occasional manual migrations)
Best for: a NAS or homelab that already runs a reverse proxy and/or other Docker containers.
Differences
The two methods install the same version AliasVault: they differ mainly in how TLS, updates, and the surrounding setup is handled.
| 🚀 Install Script | 🛠️ Docker Compose | |
|---|---|---|
| TLS/SSL | Automatic (Let's Encrypt) | Bring your own reverse proxy |
| Updates | Guided via install.sh | Manual docker pull |
| Containers | Multiple (one per service) | Single all-in-one image |
| Best for | Dedicated VM / VPS | Existing homelab / NAS |
| Build from source | Supported | Pre-built image only |
Not sure yet? You can switch later. Both methods use the same Docker bind-mount directories (/database, /certificates, /logs, /secrets), so migration is straightforward. Stop or uninstall one method, then follow the installation steps for the other. Your data is preserved.
Frequently Asked Questions
What are the system requirements?
Minimum:
- 64-bit Linux OS (Ubuntu or RHEL-based recommended)
- 1 vCPU, 1 GB RAM, 16 GB disk
- Docker CE (≥ 20.10) and Docker Compose (≥ 2.0)
Network:
- Ports 80 and 443 available
- Optional: ports 25 and 587 for private email domains