Bitwarden - Self-hosted application
Bitwarden is commonly used as a self-hosted alternative to 1Password, LastPass, Dashlane. Replacing a SaaS tool with a self-hosted equivalent lets you avoid recurring subscription fees, keep full control of your data, and continue working even when the original vendor changes pricing, ships limits, or shuts down.
License: AGPL-3.0. Built with: C#, TSQL, Handlebars, Rust, HTML, Shell, JavaScript, Dockerfile, PowerShell, PLpgSQL, SCSS, CSS. Website: https://bitwarden.com/. Source: https://github.com/bitwarden/server.
Official self-host install guide: https://bitwarden.com/help/install-on-premise-linux/ -- For lightweight self-host, see Vaultwarden: https://github.com/dani-garcia/vaultwarden/wiki
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
2 GB RAM minimum (4 GB recommended), 10 GB disk, x86_64 Linux with Docker and Docker Compose. ARM64 supported. Requires HTTPS for normal client behaviour.
Pick Bitwarden self-hosted if you need a vendor-supported password manager with enterprise SSO, SCIM directory sync, or formal compliance certifications. The official server runs as a multi-container stack on ~2 GB RAM minimum and is the right choice for organisations that need vendor support and are willing to manage that footprint. For homelabs, families, or small teams who just want Bitwarden clients with a featherweight server, the community Vaultwarden project is the more practical choice and unlocks several premium features for free.
Last verified: 2026-04-19