You can run your own password vault on a cheap server you control, instead of handing every login to a company's cloud. It's a weekend project. The software is free, the server costs about five dollars a month, and when it's done, your passwords live on a box nobody else can switch off.
That's the pitch for self-hosting a password manager. The most popular cloud option is Bitwarden, and there's a way to run a Bitwarden-compatible server at home. Worth it? For most people, honestly, no. But the option is real, so here's what it actually involves.
What people actually run
Bitwarden ships an official self-hosted version, but it's heavy. It's a Docker stack with a SQL Server database, an admin panel, an attachments server, and a pile of small services. On a tiny server it barely fits.
So almost nobody runs that. They run Vaultwarden instead, a lightweight community version of the Bitwarden server, written in the Rust programming language. It's a single program, uses a simple SQLite file for storage, and sits at around 30MB of memory while idle. The official Bitwarden apps, the browser add-on, phone app, and desktop app, all talk to it without any changes.
Vaultwarden isn't made by Bitwarden. It's a separate project that's been around since 2018, and the Bitwarden company has left it alone, so running it at home is a safe bet. Businesses should still pay Bitwarden directly. A normal setup is a small Hetzner CX22 server (2 shared CPUs, 4GB of memory) for roughly five dollars a month, Debian Linux, Vaultwarden in a container, and Caddy as the front door handling the security certificate on its own. Backups run as a nightly job that copies the database file off-site.
Vaultwarden on GitHub, Hetzner
The easy parts
Moving in is painless. Bitwarden can export your whole vault to a single file, and Vaultwarden reads that exact format. Export, import, sign back in on each device, done. No data lost, no fiddling.
The apps don't change either. Bitwarden's official browser add-on has a "self-hosted" box in its settings; point it at your own web address, sign in, and it behaves like the cloud version. Same autofill. Same screens. The phone apps work the same way, with a server address field tucked in settings.
The painful parts
Email is the first wall. Vaultwarden uses email for things like resets and verification, which means you need a mail-sending account. People who try to use their own mail server tend to burn an afternoon, give up, and switch to a paid sending service. That's the usual ending.
Backups are the second, and this is the real one. Copying the database file is easy. Planning for the day the house burns down is not; encrypted copies in two places, with the keys stored somewhere safe, takes longer than the install itself.
Two smaller traps round it out. There's a brief opening on first run, before sign-ups are switched off, where a stranger who knows the address could register their own account. Closing it is one line in a settings file, but you have to remember it. Push notifications are weaker too, so the phone vault syncs on a short delay instead of instantly.
The catch nobody mentions
Here's the honest downside. You're the admin now. If the server dies, the certificate expires, or a bad update breaks the login, there's no support line to call; it's you, locked out of every password you own. The cloud version has paid staff watching it day and night. A hobby server has you, and only when you're paying attention. That's a real trade, not a footnote.
On the upside, these boxes are steady. A Vaultwarden server can run for months untouched, restarting on its own after a reboot. And a server near you often feels quicker than the cloud, because your data has a shorter trip to make.
Should you bother
Frankly, no, unless control is the whole point. Bitwarden's cloud is excellent, with real security staff, real uptime, and real people responding when something goes wrong. A hobbyist server can't match that. The free tier covers one person at no cost, and the Families plan runs $3.99 a month, billed once a year at $47.88 for up to six people. That's cheap insurance.
So the reason to self-host isn't money and it isn't safety. It's ownership. The vault sits on hardware you hold, and no company can lock the account. If that matters to you, for privacy, for a homelab hobby, or for a rule you have to follow, Vaultwarden is the cleanest path. If it doesn't, just pay Bitwarden and get on with your day.
Bitwarden Password Manager Pricing Plans, Bitwarden self-hosted docs
