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

Selfhosted

63044 readers
1102 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
[–] AustralianSimon@lemmy.world 8 points 6 days ago

I pay for their product and its totally worth. It was $10 for the longest time and much like everything in the last few years has increased price to what it is actually worth. To be honest $20 a year is still stupid cheap and worth it to keep them developing the product. Bitwarden is also one of the few password managers that hasn't had a user data breach.

[–] Lettuceeatlettuce@lemmy.ml 148 points 1 week ago (3 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 29 points 1 week ago (14 children)
[–] Lettuceeatlettuce@lemmy.ml 40 points 1 week 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 24 points 1 week ago (8 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.

load more comments (8 replies)
load more comments (12 replies)
load more comments (2 replies)
[–] Pika@hikki.team 49 points 1 week ago* (last edited 1 week ago)

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

[–] teezeh@ieji.de 33 points 1 week ago (9 children)

@Mustachius_Grumpius “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”

[–] badgermurphy@lemmy.world 89 points 1 week ago* (last edited 1 week ago) (3 children)

Unfortunately, there is no historical example where this hasn't turned predatory. It's a tale as old as venture capital has been in software development:

  • get free contributions from altruistic people donating their time and expertise to your FOSS project that you're selling
  • make a closed-source set of extensions as optional dependencies
  • slowly diverge the closed source feature set to include developer and user "must-haves" you do not contribute upstream
  • slow or functionally halt open source contributions

It is an oft-repeated long con to pull off a mass heist of donated skill and time while imposing vendor lock-in on your users through a back door.

"As the poison spread through his body, the frog cried out, “Why did you sting me? You have killed us both!”

The scorpion replied, “I couldn’t help it. It’s my nature.”

Good take. I trust you on this, if you mind me asking: What is now the alternative? A system of setting up once, let it work until hardware dies etc.

[–] lntl@lemmy.ml 29 points 1 week ago
  • Embrace
  • Extend
  • Extinguish
load more comments (1 replies)
[–] Mustachius_Grumpius@thelemmy.club 61 points 1 week ago (3 children)

yeah but its typical double speak

load more comments (3 replies)
[–] giant_smeeg@feddit.uk 32 points 1 week ago

Yup. All CURRENT, these will start to diverge...

[–] flop_leash_973@lemmy.world 21 points 1 week ago (2 children)

If there is no intention to put the screws to the user base, then why do it on the first place?

We all know how this game ends when venture capital gets involved.

load more comments (2 replies)
load more comments (5 replies)

Not surprised in the slightest sadly.

[–] irotsoma@piefed.blahaj.zone 27 points 1 week 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.

[–] Dirk@lemmy.ml 18 points 1 week ago (1 children)
[–] phx@lemmy.world 20 points 1 week 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

[–] peyotecosmico@programming.dev 17 points 1 week ago

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

[–] badgermurphy@lemmy.world 17 points 1 week ago* (last edited 1 week ago) (2 children)

Does anyone know if there's any chance for a fork before this situation inevitably deteriorates? I dont know the license on that software enough to know if its an option.

load more comments (2 replies)
[–] PrinzKasper@feddit.org 15 points 1 week ago

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

load more comments
view more: next ›