Vaultwarden hosting: a Bitwarden server of your own, in one click
Pick Vaultwarden from the app catalog, name it, deploy. The official Bitwarden apps and browser extensions log in to your address; the vault is encrypted on your devices and stored under /data on ours.
What you get
- The official Vaultwarden image with its address set as the DOMAIN it needs for attachments and two-factor.
- Sign-ups from the web vault at your address; turn them off from the admin page once your accounts exist.
- An optional admin page, unlocked by the admin token you set when you deploy.
- The data under /data, backed up daily on paid tiers.
Sizing
Vaultwarden is a small Rust program: a family or a small team fits in the free tier's 256 MB with room to spare. On the free tier the address sleeps when idle and wakes on the next request, which the apps handle: they retry. A paid tier keeps the address awake for $2 a month.
Keep a copy
Passwords are the one thing you do not want to lose with a host. Turn on the $1 a month backups on a paid tier, and export your vault from the Bitwarden app now and then; the export is encrypted with your master password.
Frequently asked questions
Is this Bitwarden?
It is Vaultwarden, the community server that speaks the Bitwarden protocol and works with every official Bitwarden client. Bitwarden's own server is a different, much heavier program.
Is it safe to host passwords this way?
The vault is encrypted on your devices with your master password before it reaches the server, so the server only ever stores ciphertext. Use a long master password, turn on two-factor, and keep backups.
Can I use my own domain?
Yes. Point a CNAME at the app and set that domain in the app's environment as DOMAIN, then log the clients in there.
What happens on a deploy?
The repository is cloned at your branch, dependencies install, the build runs when there is one, the app starts. With auto-deploy on, every push does the same. The live console shows each step; a failed one is explained in plain words.