You can already see them positioning themselves to start removing features with the phrase "free plan."

Nothing stopping them from limiting the number of passwords available in "the free plan" or something, pressuring users into "the pay plan."

But I'm pretty cynical.

pass https://www.passwordstore.org/ keepass https://keepass.info/

Never made any sense to me why so many people ran away from these two open source options towards Bitwarden.

I never understood the 9000iq move to give all your credentials to someone else...

That's why I use "pass" as password-store.

Keepass X Syncthing

syncthing runs on everything and is easy to configure.

If you have a Nextcloud server, you should try Passman.

I use UNIX pass utility, it's very minimal and works for me

I've been using Dashlane for years and love it

Because the new CEO seems to really be wanting to find revenue and this step just reaffirms in my mind that he’s likely going to start reducing features for unpaid accounts.

It's only a matter of time. Quietly private -> publicly private -> remove features from free. It's inescapable. The stockholder greed compels them.

If you read their announcement carefully you'll find things like

All current features are available in both versions

Which strongly implies that the different versions will start to diverge over time. Then at one point they will just be like maah it's not worth putting more work into the open source thing, we'll focus on building new cool features yada yada yada. And this is how all the open to partly open to closed source rug pulls worked in the last years.

(If you want to do this the worst way possible like MinIO you also squash / delete the Git history the moment you announce you're only working on closed source)

Before Bitwarden / Vaultwarden I went with Keepass (it was some fork don't remember the exact name KeepassXC probably) synced via Nextcloud. It's not as convenient as Bitwarden plus at least back then it didn't support passkeys. So yeah, I don't know what is actually out there. Honestly I don't think it's super urgent to start hunting for alternatives but probably we should have at least some ideas in case the Bitwarden team does some weird moves.

Then we will shit ... the enshitification exodus goes on

Yeah, keyguard is pretty good

How often do you update vaultwarden? This has never been an issue for me.

The vault gets synced to your devices. So even if your Backend goes down you dont lose access to your passwords in an instant

3-2-1 backups guys

Yeah vaultwarden and photos are the 2 things i'm too nervous to selfhost. I do selfhost basically everything else but these 2 things are too important for me to mess up that I just don't...

There seems to be only one Android client, and it's been archived on Github. I kinda need an android client for a password manager to be usable.

Are the clients usable or is the user experience more like KeePass (i.e. bad)?

It has become Keep Ass.

Yep, ChiPass is a good replacement: https://codeberg.org/ChiPass/ChiPass

Honestly their description of use and why that use it is not concerning. I'm more concerned with their choice being copilot lol.

Yup, I was supposed to say KeepassXC. (...I mean I probably considered using KeepassX at some point, it's XC's predecessor after all. But as I recall Keepass 2 worked well enough on Mono, so I didn't need to switch.)

Also, whoopsies on XC's AI use. At least they don't seem to embrace it as much as Bitwarden, but still makes me go hmm.

They never vibe code though:

This process is fully transparent and open for anyone to see, and it does not change with AI. We take no shortcuts. At KeePassXC, we use AI for two main purposes:

As an additional pair of “eyes” in code reviews.
In this function, AI summarises the changes (the least helpful part) and points out implementation errors a human reviewer may have missed. AI reviews don’t replace maintainer code review, nor do they relieve maintainers from their due diligence. AI code reviews complement our existing CI pipelines that perform unit tests, memory checks, and static code analysis (CodeQL). As such, they are a net benefit and make KeePassXC strictly safer. Some examples of AI reviews in action: example 1, example 2.

For creating pull requests that solve simple and focused issues, add boilerplate code and test cases.
Unfortunately, some people got the impression that KeePassXC was now being vibe coded. This is wrong. We do not vibe code, and no unreviewed AI code makes it into the code base. Full stop. We have used Copilot agent to draft pull requests, which are then subsequently tweaked in follow-up commits, and reviewed by a maintainer, openly for anyone to see, with the same scrutiny as any other submission. Good pull requests are merged (example), bad pull requests are rejected (example).

So these changes affect the client app too? If that's the case can't the client app be replaced?

At that point the only thing that would remain is the protocol itself

Only if you are reselling bitwarden. The client apps are still free for personal use.

The protocol is the same, anyone can build an app.