Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs.
Vaultwarden is commonly used as a self-hosted alternative to 1Password, LastPass, Bitwarden. 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: GPL-3.0. Built with: Rust, JavaScript. Website: https://github.com/dani-garcia/vaultwarden. Source: https://github.com/dani-garcia/vaultwarden.
This will preserve any persistent data under `/vw-data/`, you can adapt the path to whatever suits you. ### Docker Compose To use Docker compose you need to create a `compose.yaml` which will hold the configuration to run the Vaultwarden container. ```yaml services: vaultwarden: image: vaultwarden/server:latest container_name: vaultwarden restart: unless-stopped environment: DOMAIN: "https://vw.domain.tld" volumes: - ./vw-data/:/data/ ports: - 127.0.0.1:8000:80
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.
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Vaultwarden. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-04-21