A self-hosted password manager keeps your password vault on a server you run, instead of on a password company's cloud. The apps on your phone and laptop work the way they always do, but they sync with your own server. This guide compares the main options, explains what self-hosting does and does not improve, and walks through setting up Vaultwarden, the most popular choice, on a VPS.
The short version
For one person or a family, run Vaultwarden on a small VPS behind HTTPS and use the official Bitwarden apps with it. For a team that shares credentials, look at Passbolt. If you do not want a server at all, use KeePassXC and sync the file yourself. Whichever you pick, self-hosting moves the work of updates, backups and uptime onto you, so only do it if you will keep up with that.
What a self-hosted password manager changes
A good cloud password manager already encrypts your vault on your device before it uploads anything, so the company cannot read your passwords. Self-hosting does not make that encryption stronger. What it changes is everything around it:
- Where the encrypted vault lives. It sits on your server, not in a shared database holding millions of other vaults, which makes it a much less attractive target.
- Who holds your account data. Your email address, devices and login history stay with you instead of a third party.
- Which country's law applies. You choose the jurisdiction by choosing where the server runs.
- Who is responsible. You are. If you miss an update, lose the server without a backup or let the certificate lapse, nobody else will fix it.
That last point is the real cost. A self-hosted password manager is worth it if you want control and will maintain it. If you want something you never have to think about, a reputable cloud service is the safer choice.
The main options compared
Best for most peopleVaultwarden
An unofficial server written in Rust that works with the official Bitwarden apps and browser extensions. The project describes it as aimed at individuals, families and smaller organisations, for cases where the official server would be too resource-heavy. It is open source under the AGPL-3.0 licence and not affiliated with Bitwarden, Inc. In 2024, Germany's Federal Office for Information Security (BSI) had version 1.30.3 reviewed. The review found two vulnerabilities rated high, and the developers fixed the most serious issues in version 1.32.0 that August. That shows the code gets outside scrutiny, not that newer versions are free of bugs.
Trade-offs: it does not implement every feature of the official server, new Bitwarden features can take a while to arrive, and support comes from the community, not a company.
OfficialBitwarden self-hosted
Bitwarden's own server, in two forms. The standard deployment is built for businesses and asks for at least 2 GB of RAM and 12 GB of storage, with 4 GB and 25 GB recommended. Bitwarden lite, which left beta in December 2025, is a single container for personal use and home labs, and needs at least 200 MB of RAM and 1 GB of storage. Both need an installation ID and key from Bitwarden's website.
Trade-offs: some features need a paid licence, and the standard deployment needs a bigger server.
For teamsPassbolt Community Edition
An open-source password manager built for teams sharing credentials, from Passbolt SA in Luxembourg. Every secret is encrypted with OpenPGP for each person who has access to it. The Community Edition is free under the AGPL-3.0 licence with no cap on users, and it installs on Docker, Debian, Ubuntu and other Linux systems.
Trade-offs: it is built around a team workflow, so it feels heavy for one person, and features such as SSO and audit logs are in the paid editions.
No serverKeePassXC with file sync
KeePassXC stores your vault in a single encrypted KDBX file on your own device and works entirely offline. To use it on several devices, you sync the file yourself with a tool such as Syncthing or Nextcloud, and open it on your phone with a compatible app such as KeePassDX or KeePassium.
Trade-offs: there is no server to maintain, but sharing with other people is clumsy, and editing on two devices before they sync can leave you with two conflicting copies of the file.
| ย | Vaultwarden | Bitwarden lite | Passbolt CE | KeePassXC |
|---|---|---|---|---|
| Built for | Individuals, families, small groups | Personal use and home labs | Teams | Individuals |
| Needs a server | Yes, a small one | Yes, a small one | Yes | No |
| Apps | Official Bitwarden apps | Official Bitwarden apps | Passbolt extension and apps | KeePassXC and compatible apps |
| Licence | AGPL-3.0 | Bitwarden licence terms | AGPL-3.0 | Open source |
| Sharing | Organisations and collections | Organisations and collections | Per-user, per-secret | Share the whole file |
Which one should you choose?
For a self-hosted password manager that you and your family will use every day, Vaultwarden is the usual answer. It runs comfortably on the smallest VPS, and everyone keeps the polished Bitwarden apps they may already know. Choose Bitwarden lite if you would rather run the vendor's own code and accept its licence terms. Choose Passbolt if you are setting up shared credentials for a team or a company. Choose KeePassXC if you want no server at all and are happy to manage file sync.
The rest of this guide sets up Vaultwarden.
How to set up Vaultwarden on a VPS
You need a VPS with root access, a domain or subdomain you control, and about an hour. Vaultwarden runs in Docker, and the setup below uses Caddy in front of it, because Caddy fetches and renews a free HTTPS certificate on its own. HTTPS is not optional here: the Vaultwarden project notes that the web vault needs a secure context for the browser's Web Crypto API, so it only works over HTTPS.
Step 1Prepare the server and the domain
Order a small VPS with Debian or Ubuntu, log in over SSH with a key, and install updates. Install Docker Engine and the Compose plugin by following Docker's instructions for your distribution. Then create a DNS record such as vault.example.com pointing to the server's IP address, and open only ports 80 and 443 in the firewall, plus your SSH port.
Step 2Create the Compose file
Make a folder such as ~/vaultwarden and save this as compose.yaml, with your own domain in place of the example:
services:
vaultwarden:
image: vaultwarden/server:latest
container_name: vaultwarden
restart: unless-stopped
environment:
DOMAIN: "https://vault.example.com"
SIGNUPS_ALLOWED: "true"
volumes:
- ./vw-data:/data
caddy:
image: caddy:2
container_name: caddy
restart: unless-stopped
ports:
- "80:80"
- "443:443"
volumes:
- ./Caddyfile:/etc/caddy/Caddyfile:ro
- ./caddy-data:/data
- ./caddy-config:/config
Step 3Point Caddy at Vaultwarden
In the same folder, save this as Caddyfile:
vault.example.com {
reverse_proxy vaultwarden:80
}
Start both containers with docker compose up -d. After a minute, open https://vault.example.com and you should see the vault login page with a valid certificate.
Step 4Create your account, then close signups
By default anyone who can reach your server can register, so create your own account, and those of your family, straight away. Then change SIGNUPS_ALLOWED to "false" in the Compose file and run docker compose up -d again. Organisation owners can still invite people by email; set INVITATIONS_ALLOWED to "false" if you want that closed too.
Step 5Connect the apps and turn on two-step login
In the Bitwarden app or browser extension, choose the self-hosted option on the login screen and enter your server's address. Then enable two-step login in your account settings. Vaultwarden supports authenticator apps, FIDO2 security keys, YubiKey and Duo.
Step 6Leave the admin page off unless you need it
The admin page stays disabled until you set an ADMIN_TOKEN. If you do enable it, store the token as an Argon2 hash rather than plain text; the project's wiki explains how to generate one with docker exec -it vaultwarden /vaultwarden hash. Be aware that once you save settings on the admin page, they go into a config.json file that overrides the matching values in your Compose file.
Step 7Set up backups before you rely on it
Everything lives in the vw-data folder, but a copy of the database alone is not a full backup. The project's backup guide says to copy the SQLite database with its .backup command rather than copying the file while Vaultwarden is using it, and to keep the attachments and sends folders, the rsa_key files and config.json if it exists.
Install the SQLite command-line tool with apt install sqlite3, then save this as backup.sh in your vaultwarden folder. It saves the database and the other files, and deletes backups older than 30 days:
#!/bin/sh set -e cd "$(dirname "$0")" mkdir -p backups STAMP=$(date +%F) sqlite3 vw-data/db.sqlite3 ".backup 'backups/db-$STAMP.sqlite3'" tar -czf "backups/files-$STAMP.tar.gz" --exclude='db.sqlite3*' --exclude='icon_cache' --exclude='tmp' -C vw-data . find backups -type f -mtime +30 -delete
Make it executable with chmod +x backup.sh and run it once by hand to check that both files appear in backups. The files in vw-data belong to root, so add the script to root's crontab with sudo crontab -e and a line such as 30 3 * * * /home/you/vaultwarden/backup.sh, using your own path, to run it every night at 03:30. Keeping the commands in a script also avoids a cron quirk: a % sign typed straight into a crontab line is read as a line break.
A backup that only lives on the same VPS disappears with it, so copy the backups folder to a second machine every day, ideally encrypted, with a tool such as rsync or restic. Then test a restore once on a spare machine: put the database copy back as vw-data/db.sqlite3, delete any db.sqlite3-wal file, unpack the files archive into vw-data and start the containers. You will know it works before you need it.
Step 8Keep it updated
Update the containers regularly with docker compose pull followed by docker compose up -d, and keep the server's operating system patched. A password server that never gets updated defeats the point of running one.
Two things worth knowing before you start
Watch outInstant mobile sync goes through Bitwarden
Vaultwarden can push changes to the mobile apps instantly, but only through Bitwarden's push relay. You request an installation ID and key from Bitwarden, and your devices register with Bitwarden's push service. It also only works with apps from the official app stores, not from F-Droid. Without it, the mobile apps pick up changes when you open or refresh them. If keeping Bitwarden out of the chain matters to you, leave push off.
Watch outEmail is optional, but port 25 is often closed
Vaultwarden runs without email, but invitations, email verification and email-based two-step login need an SMTP server. Many VPS providers, including us, close outbound port 25 by default, so point Vaultwarden at a mail provider's submission port instead.
Where to run your password server
Vaultwarden is light, so the smallest VPS is enough for a household. Bitwarden's standard deployment needs at least 2 GB of RAM. The bigger question is where the server sits and who runs it.
Your vault items are encrypted on your devices with a key derived from your master password, so the server stores them in encrypted form. Your email address and device records are not encrypted that way, and anyone running the machine underneath your VPS can technically reach its disk and memory. Our guide to whether your hosting provider can see your data explains what that means in practice. That is why the jurisdiction and the host's own policies matter, and why a strong master password matters most of all.
We run an anonymous VPS in Switzerland and Finland that suits this well. Plans start at EUR 9.90 a month in Finland and EUR 13.90 in Switzerland, as full KVM virtual machines with root access and a dedicated IPv4 address, so Docker runs as it would on your own hardware. Signup takes an email address and a password, and you can pay in Bitcoin or Monero through our own BTCPay Server. Our 30 day money back guarantee covers shared and WordPress hosting, not VPS plans. To choose between the two countries, see Finland vs Switzerland for hosting, and for other services that can share the same server, see our list of things you can host on a VPS.
FAQ
Is a self-hosted password manager safer than Bitwarden's cloud?
Not automatically. The encryption is the same, because the vault is encrypted on your device either way. A self-hosted password manager keeps your vault and account data off a large shared target and in a jurisdiction you choose, but it is only as safe as your updates, backups and server security.
Is Vaultwarden safe to use?
It is widely used and open source, and its code has had outside review. A 2024 review of version 1.30.3 for Germany's BSI found two vulnerabilities rated high, and the developers fixed the most serious issues in version 1.32.0. Security fixes have kept coming since, as with any actively developed software, so its safety depends on keeping it updated, running it behind HTTPS and closing signups once your accounts exist.
Can I use the official Bitwarden apps with Vaultwarden?
Yes. Vaultwarden is built to work with the official Bitwarden apps and browser extensions. Choose the self-hosted option on the login screen and enter your server's address.
What happens if my server goes down?
Bitwarden says its apps keep an encrypted copy of your vault while you stay logged in, so you can still read your passwords offline, though you cannot edit them until the server is back. It says offline sessions expire after 30 days, or 90 days on mobile. One catch reported on Bitwarden's community forum: if the server answers with an error, for example a proxy page while Vaultwarden is down, the apps may log you out rather than fall back to the cached copy. Daily backups make sure you can rebuild either way.
How much does it cost to self-host a password manager?
The software behind each self-hosted password manager in this guide is free. You pay for the server and a domain. A small VPS is enough for Vaultwarden, and you can reuse a domain you already own by adding a subdomain.
Sources
- Vaultwarden on GitHub (project description, licence, HTTPS requirement)
- Vaultwarden wiki: Enabling HTTPS, Enabling admin page, Backing up your vault, Disable registration of new users, Disable invitations, Enabling Mobile Client push notification and Audits
- BSI press release on its code analysis of KeePass and Vaultwarden (in German), 14 October 2024, and heise online's report on the findings (fixes in version 1.32.0)
- Bitwarden Help Center: Lite Deployment and Linux Manual Deployment (system requirements, installation ID and key)
- Bitwarden blog: Configuring Bitwarden Clients for Offline Access
- Bitwarden Community Forums: "Bitwarden App Logs Out if the server is not running"
- Passbolt: Community Edition documentation and licence
- KeePassXC project documentation
Last reviewed: 19 November 2026
Research note: Software features and system requirements change between releases; the details above reflect each project's documentation as of the review date. The setup steps are a starting point for a personal server, not a full hardening guide, so read the Vaultwarden wiki before running it for other people.
Shared Hosting
WordPress Hosting
VPS Hosting
Dedicated Servers