AliasVault

AliasVault is a self-hosted password manager with a built-in email alias system. The premise is that every service you sign up to gets its own unique alias email address — not your real address. If that service is breached, sells your data, or starts spamming you, only the alias is exposed. You disable it, and the damage stops there. Your real inbox and your identity stay private.

What separates AliasVault from using a password manager alongside a separate alias service is that both pieces live in one self-hosted stack. The alias management, the vault, and a built-in email server that receives messages sent to your aliases are all part of the same deployment. You do not need a SimpleLogin subscription or a separate AnonAddy instance alongside your Bitwarden server.

End-to-end encryption means the server holds only ciphertext. Neither your passwords nor your alias configurations are readable by the server operator — which matters most when you are your own operator and want assurance that a database compromise does not expose your credentials.

The practical requirement beyond Docker is a working mail server setup. For alias email to be received and forwarded reliably, your domain needs correct SPF, DKIM, and DMARC DNS records, and your server’s IP needs a clean sending reputation. Self-hosting email is inherently more involved than self-hosting a web application, and deliverability to major email providers requires deliberate configuration. For users already comfortable running a mail server, this is familiar territory. For everyone else, it is the part that requires the most preparation before the alias feature becomes reliable.

AliasVault: Pros & Cons