Yeah I'm done with cloud providers for this shit, I'm going all in for Keepass
I just migrated to keepassxc last night!
I still wish there was something where it had better syncing conflict management than KeePass but wouldn't make you unable to do anything or randomly make your passwords completely inaccessible if you or your server went offline like Bitwarden.
I run vaultwarden at home without access to it from the outside world and once the sync is done I can be offline without issue.
God, capitalism sucks
How will this affect vaultwarden? I've been using it for 5 years and absolutely love it. I'm worried that I'll need to switch to something else though?
The Article says:
A Note for Vaultwarden Users
Whether self-hosting stays viable long-term is the real question worth sitting with.
Right now it works because Bitwarden’s clients are open source and the server API is public. Vaultwarden implements that API, and the official apps can’t tell the difference. That depends on Bitwarden continuing to publish open source clients and not restricting which servers they’ll talk to — neither of which is guaranteed under new management.
The brake on the worst case: self-hosting is a listed Enterprise feature that generates real revenue. Killing it upsets paying business customers. That matters.
The catch: what Bitwarden sells to enterprises is their own official server stack, not Vaultwarden. Vaultwarden exists in a space they’ve tolerated but never endorsed. If the calculus shifts, the tolerance ends without any announcement. Just let the API drift until compatibility breaks on its own.
I don’t think that’s imminent. But I also thought the free tier commitment was ironclad, and “Always free” isn’t on the page anymore.The real safety net is that Bitwarden’s clients are Apache 2.0 licensed. A fork would need a rebrand to stay clear of the trademark — different name, tweaked UI, same engine — but that’s a speed bump, not a wall. The web vault works through any browser regardless of what happens to the apps, so worst case you’d lose autofill temporarily while a fork caught up. Inconvenient, not catastrophic. Vaultwarden itself is already proof the model works.
Watch the clients. If they go closed, the community will notice fast, and the fork will follow.
It shouldn't in theory. Worst case is if bitwarden closes source, just fork the latest current open version and use it.
Ideally, a group, either independent or joining with vaultwarden devs, can build/maintain the frontend for vaultwarden that is bitwarden.
He completely misunderstands the product. Transparency is paramount. Not trust.
Not very trust inspiring. There's a lot of flowery words encircling enshittification.
It does claim to want to always offer a free tier, but all the new values and buzzwords are funneled towards the paid versions.
Is is time block headlines with "quiet"? Its like AI decided that word gets the most clicks and its showing up everywhere.
Yeah its like those sports headlines where they try vibe you up for some trash talk
"Player A had a perfectly blunt statement about Player B"
Only to read & find out they said Player B was great, such drama lol
All just rage bait everywhere, AI or human that's the clicks plan
if you were looking for an excuse to torpedo this abomination, here it is. hosting this gargantuan stack just for an encrypted csv file? at least the client (electron) gobbles up RAM like it's free while being bug-compatible with whatever chrome version was current half a year ago.
sadly, news ain't great on the other side of the fence - keepassXC dev is all-in on vibeshitting; latest non-polluted version is 2.7.9.; works fine and the stuff they're working on is pretty far from essential. some unknown folks forked it but who's to say what their expertise is.
never thought I'd disable my autoupdate timers but here we are. keep your eyes open.
What do you mean by "gargantuan" stack? I have a single docker container for vaultwarden that was very easy to set up and it uses less than 100mb of ram.
Not sure about the client claims though. I haven't really looked into it that much. Are you saying all versions of the client and extensions of BitWarden have issues?
Can you explain the issues with KeePass? Or is there another thread?
the dev vibecodes; I make a distinction between using the crap as a boilerplate helper and a full-blown agentic "hey computer, do this but do it super-good!". not only that, they got a super-asshole vibe as they removed claude traces from the repo and then flaunted that it's so people won't know what parts were vibeshat. "good luck finding the cutoff point", I'm paraphrasing here.
to each their own, but that's a hard pass for that fork from me.
A password manager is literally the poster child for "I would rather it lack features, but be built carefully by an expert."
This is my unverified understanding of the situation.
KeepassXC team added Copilot to their workflow to manage PRs and code some basic (according to KeepassXC) stuff.
OOP is AI writing about AI
This is really disappointing... I figured the open source nature of Bitwarden would save it from enshittification but as the author says, in the end, the company doesn't need to keep it open source.
As soon as VC money comes in, the founders cash out and the enshittification begins as the VC will be expecting returns on their money.
Vaultwarden will survive. Since the client is open source, once they close the API and break compatibility of the clients with Vaultwarden, the old version of the app can simply be forked and rebranded. I also do hope that the KeyGuard app will continue to support vaultwarden as well since if bitwarden closes the API and makes a breaking change, as is likely to happen, it will break KeyGuard as well, but it will still work with VaultWarden for some time.
The real issue is that many people who are using Bitwarden aren't savvy enough to host Vaultwarden in a secure way. Many people are careless with things like secret keys and such and dont know how to properly secure a web facing app or a VPN into their local network. But anyone who self hosts should result learn those things anyway. This one just happens to be a particularly high risk since it contains all of your passwords for everything else.
This is why despite me self hosting some things I don't rely on vaultwarden. I'm a flawed person and my family has no idea about anything. I don't need to stretch my imagination very far to think of a handful of reasons why it would fail my situation. I'll gladly pay for a password manager to not have to deal with that.
Same! I self host a number of things, but I just didn't trust myself with something as important as this. I had been paying for bitwarden even though the free plan was sufficient, just to show support. But obviously not if they go this route. I will also gladly pay for a password manager to not have to deal with that.
damn I just migrated to bitwarden a few months back :(
I've been using it for years. But I have been waiting for this day to come. Because it always comes at some point without fail.
It always comes right after I migrate my family members. Same thing with lastpass and I'm still trying to get people off that.
You still have some time to decide which route to go. If you're on the free version, stay there, but start looking for alternatives.
Proton Pass is an option. KeePass with Syncthing works great, but it is a dramatically different and more involved workflow.
I am using both, and deleted my Bitwarden account yesterday the moment I heard about this.
Also, I can't suggest enough that you export all your credentials to an encrypted json file every now and then, and store it on an offline storage device. This is important.
thanks for all the suggestions - i’ve since moved to proton pass, not sure if I want to self host this aspect of my security stack - but will be watching closely
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
much thanks to @gary_host_laptop for the logo design :)