Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs.

Alternative implementation of the Bitwarden server API written in Rust and compatible with upstream Bitwarden clients*, perfect for self-hosted deployment where running the official resource-heavy service might not be ideal.

Note: This project was known as Bitwarden_RS and has been renamed to separate itself from the official Bitwarden server in the hopes of avoiding confusion and trademark/branding issues. Please see #1642 for more explanation.

---

    

Image is based on Rust implementation of Bitwarden API.

This project is not associated with the Bitwarden project nor 8bit Solutions LLC.

IMPORTANT: When using this server, please report any bugs or suggestions to us directly (look at the bottom of this page for ways to get in touch), regardless of whatever clients you are using (mobile, desktop, browser...). DO NOT use the official support channels.

---

Features

Basically full implementation of Bitwarden API is provided including:

• Organizations support
• Attachments
• Vault API support
• Serving the static files for Vault interface
• Website icons API
• Authenticator and U2F support
• YubiKey and Duo support

Installation

Pull the docker image and mount a volume from the host for persistent storage:

docker pull vaultwarden/server:latest
docker run -d --name vaultwarden -v /vw-data/:/data/ -p 80:80 vaultwarden/server:latest

This will preserve any persistent data under /vw-data/, you can adapt the path to whatever suits you.

IMPORTANT: Some web browsers, like Chrome, disallow the use of Web Crypto APIs in insecure contexts. In this case, you might get an error like Cannot read property 'importKey'. To solve this problem, you need to access the web vault from HTTPS.

This can be configured in vaultwarden directly or using a third-party reverse proxy (some examples).

If you have an available domain name, you can get HTTPS certificates with Let's Encrypt, or you can generate self-signed certificates with utilities like mkcert. Some proxies automatically do this step, like Caddy (see examples linked above).

Usage

See the vaultwarden wiki for more information on how to configure and run the vaultwarden server.

Get in touch

To ask a question, offer suggestions or new features or to get help configuring or installing the software, please use the forum.

If you spot any bugs or crashes with vaultwarden itself, please create an issue. Make sure there aren't any similar issues open, though!

If you prefer to chat, we're usually hanging around at #vaultwarden:matrix.org room on Matrix. Feel free to join us!

from https://github.com/dani-garcia/vaultwarden

-----

Vaultwarden

Vaultwarden is an unofficial Bitwarden server implementation written in Rust. It is compatible with the official Bitwarden clients, and is ideal for self-hosted deployments where running the official resource-heavy service is undesirable.

Vaultwarden is targeted towards individuals, families, and smaller organizations. Development of features that are mainly useful to larger organizations (e.g., single sign-on, directory syncing, etc.) is not a priority, though high-quality PRs that implement such features would be welcome.

Supported features

Vaultwarden implements the Bitwarden APIs required for most functionality, including:

• Web interface (equivalent to https://vault.bitwarden.com/)
• Personal vault support
• Organization vault support
• Password sharing and access control
• Collections
• File attachments
• Folders
• Favorites
• Website icons
• Bitwarden Authenticator (TOTP)
• Bitwarden Send
• Emergency Access
• Live sync (WebSocket only) for desktop/browser clients/extensions
• Trash (soft delete)
• Master password re-prompt
• Personal API key
• Two-step login via email, Duo, YubiKey, and FIDO2 WebAuthn (including Nitrokeys and Solokeys)
• Directory Connector support (basic implementation, no group support)
  Only version v2.9.2 and lower is supported, v2.9.3 and up use a different login method not supported yet.
• Certain enterprise policies:
  • Two-Step Login
  • Master Password
  • Password Generator
  • Personal Ownership
  • Disable Send
  • Send Options
  • Single Organization

Missing features

Issue #246 contains the comprehensive list of feature requests, both features of the official server that are missing in Vaultwarden, as well as enhancements specific to Vaultwarden.

To simplify comparison with the official server, this section summarizes the features implemented in the official server that are not currently available in Vaultwarden.

Features that may be added as time permits (contributions are always welcome):

• Bitwarden Public API / Organization API key
• Event Logs
• Live sync (push notifications) for mobile clients (Android/iOS)
• Admin Password Reset
• Certain enterprise policies:
  • Master Password Reset

Features that probably won't be added unless contributed:

• Single Sign-On (SSO)
• Groups
• Custom roles
• Certain enterprise policies (UI not open source, would probably need to be configured via admin page):
  • Vault Timeout
  • Disable Personal Vault Export

Get in touch

To ask a question, offer suggestions, request new features, or get help configuring or installing the software, please use the forum.

If you spot any bugs or crashes with Vaultwarden itself, please create an issue. Make sure there aren't any similar issues open, though!

If you prefer to chat, we're usually hanging around at #vaultwarden:matrix.org room on Matrix. Feel free to join us!

from https://github.com/dani-garcia/vaultwarden/wiki