Vaultwarden vs Bitwarden: Which one fit your VPS?
Bitwarden official server need 2GB RAM and plenty containers. Vaultwarden run everything for one small container. See which one you suppose use for your personal server.
Wetín Vaultwarden and Bitwarden self-hosted really be
Vaultwarden vs Bitwarden self-hosted na choice between two servers wey dey speak the same client API, no be choice between two password managers. Bitwarden own stack dey run about a dozen containers behind nginx, dey store everything for Microsoft SQL Server, and e dey tied to an installation ID wey you register with an email address. Vaultwarden na unofficial reimplementation of the Bitwarden client API, wey dem write for Rust, and e dey run as one container against one SQLite file. Your browser extension and your phone no fit tell dem apart, because both of dem dey answer the same endpoints.
The encryption na the same for both options. Bitwarden clients dey encrypt the vault before anything comot from the device, so the server dey store blobs wey e no fit read, and Bitwarden own the vault format for both cases. Wetin different na how much machine you rent, who dey maintain the code, which features cost money, and wetin you need back up.
The Vaultwarden README talk the project status clearly: "This project is not associated with Bitwarden or Bitwarden, Inc." Na volunteer project wey no get support desk and no warranty. One active maintainer dey work for Bitwarden and dey contribute during personal time, wey be courtesy, no be endorsement.
The three stacks wey you fit install
Most comparisons dey miss say Bitwarden ships two different self-hosted products.
Bitwarden standard. Na vendor deployment wey shell script dey drive.
curl -Lso bitwarden.sh "https://func.bitwarden.com/api/dl/?app=self-host&platform=linux" \
&& chmod 700 bitwarden.sh
./bitwarden.sh installThe installer go ask for your domain, whether e suppose request Let's Encrypt certificate, installation ID and key wey you collect from https://bitwarden.com/host by entering email address, and your region (US or EU). ./bitwarden.sh start go then pull the images and bring the stack up. Bitwarden documents 2 GB of RAM and 12 GB of storage as the minimum, 4 GB and 25 GB as recommended, plus Docker Engine 26 or newer with the Compose plugin. The database na MSSQL Express image, wey Bitwarden documents as having 10 GB maximum relational database size. If that one too small, you fit point the deployment to external database instead.
Bitwarden lite. Na this deployment dem bin dey call Bitwarden Unified before. E comot from beta and dem rename am for December 2025. One application container plus database wey you choose:
services:
bitwarden:
depends_on:
- db
env_file:
- settings.env
image: ghcr.io/bitwarden/lite
restart: always
ports:
- "80:8080"
volumes:
- bitwarden:/etc/bitwarden
db:
environment:
MARIADB_USER: "bitwarden"
MARIADB_PASSWORD: "super_strong_password"
MARIADB_DATABASE: "bitwarden_vault"
MARIADB_RANDOM_ROOT_PASSWORD: "true"
image: mariadb:10
restart: always
volumes:
- data:/var/lib/mysql
volumes:
bitwarden:
data:E accepts MariaDB or MySQL, PostgreSQL, SQLite and MSSQL, and e asks for 200 MB of RAM and 1 GB of storage. Two cautions dey inside Bitwarden own documentation. Dem document am for personal use and home labs, no be business use, and e no dey make automatic database backups. So na you go handle that work completely.
Vaultwarden. One container, straight from the project README:
docker run --detach --name vaultwarden \
--env DOMAIN="https://vw.domain.tld" \
--volume /vw-data/:/data/ \
--restart unless-stopped \
--publish 127.0.0.1:8000:80 \
vaultwarden/server:latestThe publish line bind port 8000 to loopback only, and na deliberate decision be that. Vaultwarden dey serve plain HTTP and e expect reverse proxy to terminate TLS (transport layer security) in front of am. TLS no be optional here: the web vault dey do encryption with browser WebCrypto API, wey browsers expose only for secure context. So for plain http, the login page go fail for browser before your server even get request. The full Vaultwarden install walkthrough dey cover the proxy and certificate.
How much RAM Vaultwarden dey use compare to Bitwarden self-hosted?
Vendor minimums na wetin di installer go use block you from run am if your hardware no reach, e no mean say na dat be di actual weight of di software. Di rows wey dey down here come from docker stats --no-stream on top idle installs, one user each, small vault wey no get attachments, on top Ubuntu 24.04 box wey get 4 GB of RAM. Disk space na di images plus di data directory after di first successful start.
Di data wey dey behind dis chart
[
{
"label": "Vaultwarden (SQLite)",
"idle_ram_mb": 58,
"containers": 1,
"disk_gb": 0.4
},
{
"label": "Bitwarden lite + MariaDB",
"idle_ram_mb": 470,
"containers": 2,
"disk_gb": 1.6
},
{
"label": "Bitwarden standard (MSSQL)",
"idle_ram_mb": "2,400",
"containers": 12,
"disk_gb": 6.5
}
]Vaultwarden idled at 58 MB inside one container. Di standard Bitwarden stack idled near 2,400 MB across 12 containers, and na di MSSQL container dey carry most of dat load. Bitwarden lite land between dem at 470 MB with ein MariaDB container. Run di same command on top your own box before you trust any of these figures, because dem dey change base on user count, attachments, and sync traffic, plus MSSQL dey grow ein working set di longer e dey run.
Di practical advice for small VPS: Vaultwarden with SQLite dey comfortable on top 1 GB plan, and di standard Bitwarden stack no go fit start for dere. On top 2 GB plan, di standard stack fit meet di documented minimum but e go leave very small space for di operating system, so di kernel out of memory killer fit start to dey happen. When e happen, dmesg go print one line wey show di process wey e kill, and on top this stack, na usually sqlservr. Give di standard deployment 4 GB. If di same VPS suppose hold anything beyond one vault, calculate di memory usage of di other services before you pick di plan, because one photo server like PhotoPrism or Immich need far more memory pass wetin Vaultwarden go ever need. No be every neighbour dey dat hungry, though: something like Halcyon, wey dey restyle Jellyfin library like 90s rental shop na browser front end wey dey rely on di media server wey e point to, instead of make e carry ein own database. Memory no be di only thing wey you suppose check, because one RustDesk relay for remote desktop sessions barely show for docker stats but e go finish your plan bandwidth allowance instead.
Which paid features dey free for Vaultwarden?
To run Bitwarden server no dey cost money, but dem go lock paid features until you upload licence file. Premium individual accounts and paid organisation plans wey you fit self-host, like Families and Enterprise (Bitwarden no dey allow self-host for Teams), need this licence. You go download am from the cloud web vault, go Settings then Subscription for individual, or Admin Console under Billing then Subscription for organisation, before you upload am go your own instance. Organisation licences dey tied to the installation ID wey dey inside ./bwdata/env/global.override.env. So, self-hosted organisation still get paid subscription and e still dey connect to Bitwarden cloud for billing.
Vaultwarden dey enable all these features without any licence or subscription. The project wiki list dem here:
- organisations, collections and groups
- file attachments
- two-step login with email, Duo, YubiKey and FIDO2
- Emergency Access
- Bitwarden Send
- personal API keys
- SSO through OpenID Connect
SSO na the newest one and you go configure am with SSO_ENABLED, SSO_AUTHORITY, SSO_CLIENT_ID and SSO_CLIENT_SECRET. E dey authenticate the login only. The wiki talk am clear say you still need master password and your identity provider no dey control am, because na that password dey generate the key wey dey decrypt the vault. Point SSO_AUTHORITY go the discovery issuer of a self-hosted Authentik identity provider and users go sign in there, then unlock with their master password. The value must match the issuer field wey the discovery endpoint return, without the /.well-known/openid-configuration suffix for the end.
The only thing wey you no go get from Vaultwarden na vendor support. Bitwarden get SOC 2 Type 2 and ISO 27001, dem dey publish third party audit reports and dem get private HackerOne bug bounty. Those ones dey cover Bitwarden code and service, no be the server wey you install, but if auditor ask for company wey dey back your password manager, e go hard to explain say na volunteer work you dey use.
Official Bitwarden apps dey work with Vaultwarden?
Yes. Vaultwarden dey implement client API, so browser extensions, desktop apps, mobile apps, and the bundled web vault all dey work with am. For each client, set the self hosted server URL for the environment screen before you log in, no be after.
One feature need extra configuration: push notifications go mobile apps. Without am, the app go sync when you open am or according to its own timer. So, password wey you change for your laptop no go show for your phone until you check am. Vaultwarden fit use Bitwarden's push relay, and e need installation ID and key from the same https://bitwarden.com/host page wey official installer dey use.
PUSH_ENABLED=true
PUSH_INSTALLATION_ID=<your installation id>
PUSH_INSTALLATION_KEY=<your installation key>Servers for EU region still need PUSH_RELAY_URI=https://api.bitwarden.eu and PUSH_IDENTITY_URI=https://identity.bitwarden.eu. The wiki document two traps wey you suppose know before you spend one hour debugging this. App wey you install from F-Droid or Neo Store no get Firebase support, and e no go ever receive push, no matter wetin the server do. App wey connect before Vaultwarden 1.30.2 need you clear its data so e fit register push token.
How safe e dey to use reimplementation?
Bitwarden get long history of audit wey public. Cure53 check am for 2018, 2021, 2022, 2023, 2024 and 2025, and the 2025 round cover the browser extension and autofill overlay, the core application, the desktop application, the web vault, and the RustCrypto crate and library. IOActive and Mandiant check the clients for 2024, Fracture Labs cover web and network assessments throughout 2024 and 2025, Unit 42 check the mobile apps for 2025, and the ETH Zurich Applied Cryptography Group check the cryptography for 2025.
People dey surprise say dem dey check Vaultwarden too, because dem think say nobody dey look. Germany Federal Office for Information Security (BSI) make mgm security partners test am between February and May 2024 under the Caos 3.0 code analysis project, and that review rate two findings as high. Another side, ERNW report authentication bypass wey affect versions wey dey below 1.32.5 (CVE-2024-55225), wey dem fix for November 2024. Version 1.37.0, for July 2026, ship fixes for SSRF (server side request forgery) through the icon endpoint, cross organisation cipher access, and organisation policy bypass on directory imports. Version 1.37.4, for October 2026, fix another batch, wey include one high rated flaw for organisation member revocation and issues for two factor authentication, organisation invitations, and attachments.
That history show say the project get process wey dey work for how dem dey disclose issues. E also show the area wey dey always get problem: the admin page. So, treat that page like the sensitive thing wey e be. E suppose dey off unless ADMIN_TOKEN dey set, and you suppose store hash instead of the plaintext token.
docker run --rm -it vaultwarden/server /vaultwarden hashThat command go print Argon2 PHC string (password hashing competition format) wey you go paste inside ADMIN_TOKEN. Enable HTTPS before you enable the admin page, because the token dey go inside the request and if you use plain HTTP connection, anybody wey dey the path fit read the plaintext token. That token and your backup file, no be the cryptography, na dem be the real risk, and a hardening pass over a running instance go show you how to handle both. Keep /admin off the public internet as much as you fit, and join am with normal host hardening like locking down SSH access on the server.
Wetin dey break when the official API change
Na this risk people dey underrate. Bitwarden dey ship the clients, and those clients dey update themselves from app stores overnight. Vaultwarden gats follow. When client release change the API contract, un-upgraded Vaultwarden go meet client wey don already move forward, and logins or sync go start fail for devices wey you never touch.
The release notes carry concrete example. Vaultwarden 1.37.0 talk say: "This update dey required for support with clients with version 2026.7.0+, please update before reporting any issues with dem." One month later, 1.37.2, wey dem publish on 22 August 2026, repeat the warning for clients wey dey run 2026.8.0 and newer. So server wey remain for 1.37.0 or 1.37.1 don already fall behind the apps. As of 27 October 2026, the current release na 1.37.4, wey dem publish on 5 October 2026, after 1.37.3 on 13 September 2026.
Two habits fit keep this matter boring. Pin specific image tag instead of latest, so unattended pull no fit move your server for 3am. Then monitor the release feed and upgrade deliberately. Read the notes first, because na there dem dey announce breaking changes. Dem also post the 1.37.2 warning for the project's GitHub Discussions, together with recovery steps for clients wey still misbehave after server upgrade: log out and log in again, then clear the app or extension cache. Reinstall the mobile app or extension only as last resort. For example, Version 1.35.5 invalidate every existing two factor remember token during upgrade, and that one log people out from step wey dem think say dem don save.
The standard Bitwarden deployment get the opposite side of this problem. Upgrades dey run through ./bitwarden.sh updateself and ./bitwarden.sh update, and the update dey apply database migrations. Backup wey you take before the migration no be rollback for the schema after migration. So take the backup and note the version wey dey run when you take am.
Backups, na here people dey lose dia vaults
Vaultwarden data directory na di server. Keep all dis ones:
db.sqlite3- every
rsa_key*file, includingrsa_key.pemandrsa_key.der attachments/config.jsonsends/
No copy db.sqlite3 wit cp while di container dey run. SQLite fit dey write data dat time, so di copy fit turn to corrupt database wey go look normal until you try restore am. Use di online backup API instead:
sqlite3 data/db.sqlite3 ".backup '/path/to/backups/db-$(date '+%Y%m%d-%H%M').sqlite3'"Since 1.32.1, one built-in /vaultwarden backup command dey inside di image. Anyhow you do am, di snapshot still dey di same disk as di original until you move am, so push am comot from di box wit restic snapshots to off-site storage on a schedule. Backup job wey stop dey run silently go look exactly like one wey no ever exist, so make sure di timer report im own failures for place wey you go see am, na why a self-hosted ntfy server wired to a systemd OnFailure unit dey. Di rsa_key files important reach di database: di server dey sign session tokens wit dat key, so if you restore database wit new key, e go log everybody out and break organization invitations wey dey pending.
Bitwarden standard dey backup more of imsef. Di mssql container dey write nightly database backups inside ./bwdata/mssql/backups and e dey keep am for 30 days, as long as di container dey run, and you fit force one:
docker exec -i bitwarden-mssql /backup-db.shDi directories wey you suppose keep na ./bwdata/env (environment variables, including database and certificate passwords), ./bwdata/core/attachments, ./bwdata/mssql/data, and ./bwdata/core/aspnet-dataprotection. Dat last one na wetin people dey forget. E dey hold framework level data protection material, including authentication tokens and some database columns, so if you restore di database without am, di columns wey e dey protect no go fit read again. Bitwarden lite no dey do any automatic backup at all, so if you choose lite, e mean say you must get your own dump schedule just like how you go do wit Vaultwarden.
Migration for either direction
Migration dey pass through clients, no be servers, because na clients get export and import features. So both directions use the same procedure.
Each user go export from the web vault or desktop app, create account for the new server, then import. The formats na plaintext .json, plaintext .csv, encrypted .json, and one .zip wey hold the JSON plus file attachments for individual vaults. Cards, identities, stored passkeys and SSH keys go survive only for the JSON formats, so CSV migration go silently drop dem. No export format include trash items or Sends, and organisation-owned data no dey part of individual export.
Treat plaintext export like live secret, because na exactly wetin e be: your complete vault in clear text for disk. Export am, import am, then delete am for one sitting. Never send am through email or chat.
One trap dey catch people during migration. Encrypted export wey tie to your account no fit import into different account, and moving servers mean different account by definition. Choose password-protected export option instead, because e portable.
Vaultwarden to standard Bitwarden na the harder direction, because organisation structure no dey travel inside export. You go recreate the organisation for the new server, invite the users again, and each user go import their own vault. Plan maintenance window for am instead of discovering this on the day.
Which one you suppose run?
Run Vaultwarden if na you alone, your family, or home lab for 1 GB or 2 GB VPS. Organisations, Emergency Access and Send dey free. E idle memory cost na roughly like one browser tab. Backup na one SQLite file plus small directory. Na this combination make Vaultwarden dominate self-hosted password management.
Run Bitwarden own server when other people dey depend on am professionally: company wey need support contract, compliance requirement wey specify the vendor, or enterprise features wey you don already pay for. Give the standard deployment 4 GB. Treat the licence file and installation ID as part of the deployment, no be mere paperwork.
Bitwarden lite dey for awkward middle ground. Na vendor code wey get small fraction of the weight, and this one genuinely attractive. But Bitwarden document am for personal and home lab use, and e no get automatic backups. You go carry Vaultwarden operational load without Vaultwarden free feature set. Choose am when vendor code matter to you pass features, and you dey okay to run the database yourself.
If you still dey decide wetin else the box go host, the wider self-hosting shortlist put this choice beside other services wey dey compete for the same RAM.
FAQ
Vaultwarden safe reach to use as password manager?
For personal and family use, yes, if you follow some rules. The clients dey encrypt the vault before e reach the server, so Vaultwarden no dey ever see your master password or any plaintext. People don check am from outside: BSI make mgm security partners test am between February and May 2024, and ERNW report one authentication bypass wey dem fix for 1.32.5. Make sure you dey use the latest version, keep the admin page disabled or put am behind one Argon2 hashed ADMIN_TOKEN, and always serve am over HTTPS. Any business wey need vendor support or audit documentation suppose run Bitwarden own server.
How much RAM Vaultwarden need compare to Bitwarden self-hosted?
For idle installs wey we measure with docker stats --no-stream, Vaultwarden wey use SQLite take about 58 MB for one container, while Bitwarden standard deployment take near 2,400 MB across 12 containers, and most of that na the MSSQL database. Bitwarden document say 2 GB na the minimum and 4 GB na wetin dem recommend for the standard stack, and 200 MB for Bitwarden lite. Vaultwarden fit run on top 1 GB VPS and e go still get space.
I need Bitwarden licence to self-host?
No, if na free individual vault you want. To run the server na free. You need licence file to unlock premium individual features and paid organisation plan, and Families and Enterprise na the only organisation plans wey Bitwarden allow you self-host. You go download am from the cloud web vault and upload am go your instance, and dem dey issue organisation licences based on the installation ID wey dey inside ./bwdata/env/global.override.env. Vaultwarden no need any licence and e dey enable the organisation features by itself.
I fit move from Vaultwarden go Bitwarden later, or come back?
Yes, you fit move for both directions, through the clients. Each user go export their vault from the web vault or desktop app and import am go the new server after dem create account for there. The .zip export dey carry attachments for individual vaults, and the JSON forms dey carry cards, identities, passkeys and SSH keys. Trash items and Sends no dey inside any export format, and items wey organisation own, na owner suppose export dem separately, so make you plan to recreate the organisation and re-invite users for the new server.