Run a compatible password server on lightweight home hardware
Imagine hosting a password vault on a home server or small cloud instance and connecting to it with official clients while retaining direct control over your data. This project provides an alternative server compatible with existing Bitwarden apps, avoiding the high specifications required by the official Bitwarden server. Written in Rust, it uses fewer resources while meeting the security needs of individuals and small organizations.
Why use the Bitwarden apps as-is
This server implements the Bitwarden client API almost perfectly, allowing users to connect their existing official Bitwarden clients, including mobile, desktop, and browser extensions. Core features such as personal vaults, Send, attachments, website icons, and personal API keys are all supported. Organization features include collections, password sharing, member roles, groups, event logs, admin password resets, directory connectors, and policy management. It also supports various two-factor authentication methods like authenticators, email, FIDO2 WebAuthn, YubiKey, and Duo, along with emergency access.
Installation and runtime environment
The recommended installation method is to use a container image, which can be pulled from ghcr.io, docker.io, or quay.io and run with Docker or Podman. A host volume must be mounted for persistent data storage, with the example using the /vw-data/ path. Because the Web Vault requires HTTPS and a secure context for the Web Crypto API, enabling HTTPS is mandatory. Although based on the Rocket web framework, a reverse proxy is recommended for TLS configuration. Community packages exist but may not be the latest version or may have different configuration methods, so caution is advised.
Data loss and scope of responsibility
This project is not officially associated with Bitwarden Inc. While one maintainer is employed by Bitwarden, they contribute in their personal time independently, with other maintainers reviewing the work. The project's direction focuses on sustainability for the self-hosting community, specifically individuals, families, and small organizations. It is important to note that the developers are not responsible for data loss. Users are responsible for regularly backing up all information, including passwords and attachments, and must contact the developers immediately if data is lost.
Pre-use checks
Do not use official Bitwarden support channels; instead, report bugs or suggestions directly to this project's issue tracker or community forum. It is advisable to first check if you are using the latest version and if similar issues have already been reported. This alternative server is suitable for environments where the resource-heavy official server is a burden, but a data backup strategy must be established. The README does not explicitly mention licensing or specific enterprise support scope, so additional verification is needed if these aspects are important.
