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

Selfhosted

63012 readers
1126 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
400
Bitwarden Switches to Commercial License (community.bitwarden.com)
submitted 1 week ago* (last edited 1 week ago) by Mustachius_Grumpius@thelemmy.club to c/selfhosted@lemmy.world
149 comments fedilink hide all child comments
 

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
you are viewing a single comment's thread
view the rest of the comments
[–] lemmyvore@feddit.nl 24 points 1 week 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 5 points 1 week ago (1 children)

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

[–] Natanox@discuss.tchncs.de 20 points 1 week ago (2 children)

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

[–] nibbler@discuss.tchncs.de 7 points 1 week ago (1 children)

History shows this will happen. Or do you have any counter example?

Mariadb, libreoffice and most recently OpenCourant

[–] Natanox@discuss.tchncs.de 5 points 1 week ago (1 children)

Not arguing against it of course, just dislike when people make forking (and establishing a whole new standard) sound like not that big of a deal.

[–] nibbler@discuss.tchncs.de 0 points 1 week ago (1 children)

well, the first step of forking is clicking a button or execting a "git clone" command. thats trivial. publishing to android is a bit of work, but very one-time.

keeping up with development is a different story - but many foss projects thrive with support from whoever needs to have something fixed.

[–] Natanox@discuss.tchncs.de 4 points 1 week ago (1 children)

You'll also have to convince other maintainers to adopt the new API in this case, otherwise it's pointless. Vaultwarden is only the server, you'd at least require one third-party client (e.g. Keyguard) to add and maintain the Vaultwarden API and probably also someone to fork the browser plugins. This whole issue is quite involved.

[–] nibbler@discuss.tchncs.de 3 points 1 week ago

I highly doubt future compatibility. Things will diverge. I care about having a good hostable password manager. I don't care about the name of the client or if it's compatible with some closed source shit.

[–] ryannathans@aussie.zone 0 points 1 week ago

When presented a hypothetical between the commenter suggesting it be

A) forked now

And me suggesting

B) forking when there is a problem

You elect C) the commenter does the work?

Brilliant contribution