this post was submitted on 10 Oct 2026
245 points (98.8% liked)

Selfhosted

62867 readers
812 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

RyanL Bitwarden Employee

Hello everyone!

Starting in the next release, the Bitwarden apps published to the various stores will be the commercially licensed builds. No action is needed, and the apps will work exactly as they do today.

Bitwarden remains committed to open source security and transparency
The GPLv3 OSS licensed version continues to be updated and published on GitHub
All current features are available in both versions
License details are on GitHub
Bitwarden remains committed to a robust, free forever plan for everyone

If you have any questions, please ask them in this thread. Thanks all!

EDIT:

Bitwarden is not going closed-source
You can still fork Bitwarden
No change to self-hosting, the licensing change affects those who are repackaging and reselling Bitwarden
The free plan is here to stay permanently
top 50 comments
sorted by: hot top controversial new old
[–] Dirk@lemmy.ml 9 points 4 hours ago (1 children)
[–] phx@lemmy.world 8 points 2 hours ago

This seems to be clients for the end devices, which I'm worried may actually be a move towards locking out VaultWarden which will uses the BW Clients

[–] Lettuceeatlettuce@lemmy.ml 69 points 7 hours ago (1 children)

Well, we all know how this ends...

It's a really sad day for me, I love Bitwarden, it's easily the best password manager I've used, and I'm in IT, I've used a bunch.

Fuck private equity, fuck it to death. But until then, I'll be moving my test setup for KeyPassXC into production over the coming weeks and months.

I was happily subscribed to Bitwarden for years for my personal account, I moved several people and a whole company onto it's platform. We had a good run, time to move on.

[–] nibbler@discuss.tchncs.de 17 points 7 hours ago (3 children)
[–] Lettuceeatlettuce@lemmy.ml 13 points 4 hours ago

If I'm going to have to host my own infrastructure, I don't want it tied to Bitwarden, given the new direction of the company.

I fully support Vaultwarden though, and I wish them well.

I'll be going with KeyPassXC and Syncthing.

[–] lemmyvore@feddit.nl 4 points 4 hours ago (1 children)

Vaultwarden (and all the client apps) depend on Bitwarden for the API spec. If Bitwarden introduces closed features in the API that Vaultwarden can't/won't implement, but the client apps do, it will split the spec. They can also introduce API license keys, which would render Vaultwarden mostly irrelevant.

The only way for Vaultwarden to remain relevant going forward is to own it and split ways from Bitwarden. This would in turn mean that the FOSS client apps have to decide which to support. But I think the ecosystem is going to fragment eventually anyway, so the sooner every app decides which way they want to go, the better.

[–] ryannathans@aussie.zone 2 points 2 hours ago (1 children)

Or you could just fork it when there's a problem

[–] Natanox@discuss.tchncs.de 5 points 2 hours ago

Sounds like you're volunteering to do that additional amount of work.

[–] altphoto@lemmy.today 7 points 6 hours ago (2 children)

I'm. Using Vaultgarden but its not clear if the Android app will still be available.

[–] pogmommy@lemmy.ml 9 points 5 hours ago (2 children)

I've been very happy with Vaultwarden+Keyguard

https://keyguard.dev/

[–] artwork@lemmy.world 1 points 5 minutes ago

Thank you very much for the awesome project mentioned! I had no idea about it!
The marvel works great with Vaultwarden, too, it seems!

Though, Bitwarden system/clients are not so featureful as KeePassXC, for example, it's a great alternative for a more adequate synchronization.

[–] nibbler@discuss.tchncs.de 3 points 5 hours ago (1 children)

But that's not Foss, so u didn't consider it

[–] artwork@lemmy.world 1 points 2 minutes ago

It is free and open-source on Desktop at this moment.

Keyguard is a commercial app and unlocking a premium funds its further development and supports me (Artem Chepurnyi) directly. As of right now, only the Android builds distributed via Google Play store have main features locked behind a paywall, other distribution channels have a build with everything unlocked.

Source: https://keyguard.dev/docs/premium/

But it makes sense to pay for it, since Bitwarden is a constantly changing system and these projects based on it must always be up-to-date with their API changes, too. This is time and worry consuming, and should be compensated.

[–] nibbler@discuss.tchncs.de 2 points 5 hours ago

There will be... Some fork at least

[–] peyotecosmico@programming.dev 7 points 5 hours ago

Heh, I'm looking at you to those people that looked at me weird because I told them I was good with Keepass!

[–] PrinzKasper@feddit.org 11 points 6 hours ago

Are they still going to publish the Android client app via their own F-Droid repository?

[–] irotsoma@piefed.blahaj.zone 10 points 6 hours ago

Sure, it's no change for self hosters currently, but it's one more step in moving towards a more closed platform overall. I do hope more FOSS client apps end up getting made sometime soon. I've been using Keyguard on Android for some time, which means the recent several breaking changes in the Bitwarden apps to the Vaultwarden backend haven't hit me as hard, but I do still use the official apps for my laptop and desktop and Keyguard isnt fully FOSS, of course. I'd love to see some forks or brand new apps one of these days that are actually fully FOSS for both mobile and browsers. I've thought about doing some myself, but I have too many other projects and I also don't have a MAC or want to pay the fees to make an iPhone version. And I abandoned my Android Developer account when they started the identity nonsense, so none of my apps are on the official store anymore and Fdroid and similar may not be viable soon, so it would only really be for myself and a few others who use alternate Android OS's.

[–] Pika@hikki.team 39 points 10 hours ago* (last edited 10 hours ago)

I guess we're gonna see more open-source apps soon, aimed at Vaultwarden first

load more comments
view more: next ›