vaultwarden: A Rust-based alternative server implementation compatible with official Bitwarden clients.
What problem it solves
Vaultwarden provides an alternative server implementation of the Bitwarden Client API, written in Rust and compatible with official Bitwarden clients. It is intended for self-hosted deployment where running the official resource-heavy service might not be ideal.
Key features
Compatible Bitwarden Client API — The server implements the Bitwarden Client API and is compatible with official Bitwarden clients, including mobile, desktop, and browser clients.
Source: README
Personal and Organizational Vault Features — Vault features include personal vaults, sends, attachments, organizations, collections, groups, event logs, policies, and emergency access.
Source: README
Multiple Two-Factor Authentication Methods — The implementation supports multi- and two-factor authentication, including authenticator applications, email, FIDO2 WebAuthn, YubiKey, and Duo.
Source: README
Container-Based Deployment — Container images are the recommended installation method, with persistent storage mounted from the host. The README also provides Docker Compose configuration and notes that Podman can be used in place of Docker.
Source: README, docker
Database and Deployment Options — The Rust package exposes database backend features for SQLite, MySQL, and PostgreSQL, along with an S3 integration and optional vendored OpenSSL support.
Source: Cargo.toml, migrations, diesel.toml
Quick start
Copied verbatim from the project's README.
docker pull vaultwarden/server:latest
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:latestservices:
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:80Who it may suit
Inference: May suit self-hosting individuals, families, and small organizations that want to operate their own password-management server using official Bitwarden clients.
Topics to discuss
Which deployment and database configuration should receive more detailed community documentation?
What additional compatibility scenarios should be covered by automated client testing?
How should operators be guided to configure HTTPS and a reverse proxy safely?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/dani-garcia/vaultwarden#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…