HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dani-garcia
vaultwarden
Rust2018–2026
dani-garcia / vaultwarden

vaultwarden

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

153Distinct people
182Mentions
5Explicit recommenders
70.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I recommend Vaultwarden as a bitwarden server. It's pretty quick to set up and completely open source. https://github.com/dani-garcia/vaultwarden

techjamie used a recommendation phrase. 5 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:06:00 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year182 dated mentions

Observed mentions: 2018-07-11 03:10:43 UTC to 2026-10-10 17:24:57 UTC.

010203040502018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 21 mentions; 2 submissions, 19 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 25 mentions; 4 submissions, 21 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 46 mentions; 0 submissions, 46 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 38 mentions; 8 submissions, 30 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 9 mentions; 1 submissions, 8 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 12 mentions; 1 submissions, 11 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC303
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC11011
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC21219
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC25421
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC46046
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC38830
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC17215
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC918
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC12111

From the project README

An excerpt from the repository, fetched Nov 14, 2026.

Read the project’s introduction
An alternative server implementation of the Bitwarden Client API, written in Rust and compatible with official Bitwarden clients [disclaimer], perfect for self-hosted deployment where running the official resource-heavy service might not be ideal. ImportantWhen using this server, please report any bugs or suggestions directly to us (see Get in touch), regardless of whatever clients you are using (mobile, desktop, browser...). DO NOT use the official Bitwarden support channels. Features A nearly complete implementation of the Bitwarden Client API is provided, including: Personal Vault Send Attachments Website icons Personal API Key Organizations Collections, Password Sharing, Member Roles, Groups, Event Logs, Admin Password Reset, Directory Connector, Policies Multi/Two Factor Authentication Authenticator, Email, FIDO2 WebAuthn, YubiKey, Duo Emergency Access Vaultwarden Admin Backend Modified Web Vault client (Bundled within our containers) Usage ImportantThe web-vault requires the use of HTTPS and a secure context for the Web Crypto API. That means it will only work if you enable HTTPS. We also suggest to use a reverse proxy. The recommended way to install and use Vaultwarden is via our container images which are published to ghcr.io, docker.io and quay.io. See which container image to use for an explanation of the provided tags. There are also community driven packages which can be used, but those might be lagging behind the latest version or might deviate in the way Vaultwarden is configured, as described in our Wiki. Alternatively, you can also build Vaultwarden yourself. While Vaultwarden is based upon the Rocket web framework which has built-in support for TLS our recommendation would be that you setup a reverse proxy (see proxy examples). TipFor more detailed examples on how to install, use and configure Vaultwarden you can check our Wiki. Docker/Podman CLI Pull the container image and mount a volume from the host for persistent storage. You can replace docker with podman if you prefer to use podman. 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:latest 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. 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 Get in touch Have a question, suggestion or need help? Join our community on Matrix, GitHub Discussions or Discourse Forums. Encountered a bug or crash? Please search our issue tracker and discussions to see if it's already been reported. If not, please start a new discussion or create a new issue. Ensure you're using the latest version of Vaultwarden and there aren't any similar issues open or closed! Contributors Thanks for your contribution to the project! Disclaimer This project is not associated with Bitwarden or Bitwarden, Inc. However, one of the active maintainers for Vaultwarden is employed by Bitwarden and is allowed to contribute to the project on their own time. These contributions are independent of Bitwarden and are reviewed by other maintainers. The maintainers work together to set the direction for the project, focusing on serving the self-hosting community, including individuals, families, and small organizations, while ensuring the project's sustainability. Please note: We cannot be held liable for any data loss that may occur while using Vaultwarden. This includes passwords, attachments, and other information handled by the application. We highly recommend performing regular backups of your files and database. However, should you experience data loss, we encourage you to contact us immediately. Bitwarden_RS 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 - v1.21.0 release and project rename to Vaultwarden for more explanation.
Read the full README on GitHub

What Hacker News says

46 sources
Self-hosted instance of Bitwarden works pretty well, and you can make it accessible behind a VPN to your local network only (plus there are multiple implementations of its back-end). Less-automated solutions make impractical concessions in usability. Reference impl. in C#: https://github.com/bitwarden/server Self-host friendly impl. in Rust: https://github.com/dani-garcia/vaultwarden p.s.: reference implementation is by far one of the better examples of how to do microservice-based C# solution of high code quality right.
In What’s in a PR statement: LastPass breach explained
sondr3·Dec 26, 2022Recommendation phrase
Throughout the years I've tried most of the more popular ones on the market, some times forced via work and other times because I was curious. - KeePassXC: tried this when I was looking for a self-hosted, open-source alternative to LastPass years ago. Was surprised at how well it worked, but syncing was too much of a hassle so I gave up fairly quickly. - 1Password: my favorite of the bunch so far, great UI and UX, works seamlessly across all my devices with all the stuff I want and need: credit card info, logins, 2FA, automatic hidden email generation via Fastmail, easy sharing and family accounts work really well, CLI for use in scripts and now builtin SSH-key management. Not a huge fan of the subscription model, but probably the service I am most happy to pay for. - LastPass: was forced to use this at my previous job, absolutely hated i
Read the rest
t. The UI and UX feels ten years behind 1Pass and Bitwarden, it's slow and not nearly as featureful as the alternatives. I switched from them when they were bought out by LogMeIn, but it doesn't look like the product has meaningfully changed since then. - BitWarden: played around with this for a while, but didn't switch from 1Pass mostly because I am not willing to host something like this myself and it costs the same as 1Pass with less features and polish. Personally, I would recommend 1Pass for a "it just works" and Bitwarden hosted yourself if you want the same but on your own premises via https://github.com/dani-garcia/vaultwarden.
In Ask HN: LastPass Alternatives
> is their actually a technical reason to believe they are better than Lastpass or any of their competition (have they like open sourced all their stuff?). You can see their server and client code here: https://github.com/bitwarden I choose to use their clients unmodified, along with an instance of the server formerly known as "bitwarden_rs" running in my basement as the sync backend. https://github.com/dani-garcia/vaultwarden I still pay them annually for their "freemium" features even though I prefer not to let them host my data.
In The situation at LastPass may be worse than they are letting on
Feel free to respond if you're willing to address any of my points in good faith. I've made it abundantly clear I only believe in audited, well behaving and open source solutions. I'm not advocating for sending your passwords off to an unknown entity in clear text. My point about self-hosting password managers was aimed at a relatively common (but in my opinion, unwise) advice for people to just host their own instances of vaultwarden[1], but it also applies to file-based storage such as KeePass. [1] https://github.com/dani-garcia/vaultwarden
In LastPass breach is worse than you think because URLs were unencrypted
If self-hosting is an option for you (that already partly resolves not having to deal with 'shady companies', or at least you can choose a hoster yourself); I've been using Vaultwarden[1] to great satisfaction for about a year now and would recommend it. I don't think it does password history, but as you're in control of the hosting environment you could add that yourself. Must say I don't see the use of password history though - why is that useful? [1] https://github.com/dani-garcia/vaultwarden.git
In Ask HN: Password manager that doesn't suck?
When you put it that way, I agree - a password manager should really be implementable as a single statically linked binary. There seem to be some other Docker features used, like healthcheck [0], and MariaDB seems to be installed, too, so it might be worth considering how much additional OS-dependent complexity would the equivalent functionality without using Docker require. At the very least, you need some kind of service manager to run your program on boot, and restart it on error. At that point, Docker may as well be used as a glorified service manager - just slap your static binary in a `FROM scratch` container, and you're done. > I am not a fan of this kind of redundancy and opaqueness. Me neither. But I wouldn't blame Docker itself - it's just a tool. If it wasn't for Docker, some other way of circumventing good engineering would be
Read the rest
In Bring Your Own Password Manager: Portable BitWarden on a Pi Zero
One reason is that software isn't always distributed in normal distro repositories anymore. People can't (or don't want to) deal with dependency management so they ship an entire (slightly outdated version of an) OS with their application to make deployment foolproof. The vaultwarden install instructions assume Docker, for example: https://github.com/dani-garcia/vaultwarden. If you want to install native binaries, you're going to have to git fetch/checkout/pull the latest release tag and run `cargo build --features sqlite --release` yourself. Doable in a cronjob, but it'll probably take a compile to build a system like vaultwarden on a low-power ARM core.
In Bring Your Own Password Manager: Portable BitWarden on a Pi Zero
This is a long but satisfying road if you're a tinkerer. Start by prioritising. In my case, I was worried about Google locking me out so I started there, other things such as VPN could wait because I wasn't locked in on my VPN service. In your case that might be migrating your photos off iCloud. I found the awesome-selfhosted[1] list to be excellent for trying out different products that match the size of the VPS you've got or maybe you just want to put that onto your local Synology NAS if you don't need your whole photo roll on the go. Self hosted BitWarden is also another good starting point with the very lightweight vaultwarden[2] just make sure you always know where your vault is stored on your server and make backups. While it's a long road it doesn't need to consume your life daily but it still requires you to keep up with all the t
Read the rest
hings any sysadmin needs to handle like monthly patching, monitoring the logs for sustained abuse and break in attempts. Subreddits /r/selfhosted and /r/homelab are also great places to have a browse. [1] https://github.com/awesome-selfhosted/awesome-selfhosted#pho... [2] https://github.com/dani-garcia/vaultwarden
In Ask HN: How can a total beginner start with self-hosting?
Vaultwarden [0] is under the GPL, which is probably the software you are going to run anyway since it's lighter. The server is basically only a dump pipe since encryption is done client side so there's no need to use the official one. Also Bitwarden's software has multiple licenses, one of them being AGPL for the server and one of them being GPL for the client. The part of the code that's under the Bitwarden license which you have to pay for is SSO, SCIM and I think FIDO2 authentication as they use some Azure tools for all of these and as such they can't run on premises Quoting from their license FAQ [1]: > "In your GitHub repositories, how can I determine what license applies to a given software program?" > "Each Bitwarden repository contains a LICENSE.txt file that spells out which license applies to the code in that repository." > "In
Read the rest
the case of the Bitwarden server repository, the files are organized into various directories. These directories are not only used for logical code organization, but also to clearly distinguish the license that a given source file falls under. All source files under the /bitwarden_license directory at the root of the server repository are subject to the Bitwarden License. If a file is not organized under the /bitwarden_license directory, the AGPL 3.0 license applies." Vaultwarden offers those for free if you so wish, but there are no restrictions to self hosting Bitwarden. [0]: https://github.com/dani-garcia/vaultwarden [1]: https://github.com/bitwarden/server/blob/master/LICENSE_FAQ....
In Bitwarden: Avoid at all costs (outage issue)
I've been using Bitwarden's clients (browser extension, mobile apps, desktop apps) with a self-hosted vaultwarden [1] server. It's marginally free if you are already self-hosting other stuff. I'm hosting it on a raspberry pi 4b at home and exposing it to public Internet through Cloudflare zero trust (also free). Had no problems so far. [1] https://github.com/dani-garcia/vaultwarden, note that it's different from Bitwarden's official server (https://bitwarden.com/help/install-on-premise-linux/), uses less CPU/memory, and enables premium features like TOTP for free.
In Bitwarden: Avoid at all costs (outage issue)
I use Bitwarden. I don't trust that service with my data. I host an instance of the community-developed backend: https://github.com/dani-garcia/vaultwarden on my own server so that I don't need to, and use the FOSS clients to access it. I feel more comfortable with that than syncing a KeePass file over dropbox or google drive, mostly because I got myself into a nasty situation that way with a corrupted KeePass database a while back.
In KeePass is the free, open source, light-weight and easy-to-use password manager

Showing the 15 most recent of 46 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.