this post was submitted on 10 Oct 2026
73 points (96.2% liked)

Linux

15173 readers
240 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

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
you are viewing a single comment's thread
view the rest of the comments
[–] TVA@thebrainbin.org 1 points 12 hours ago

VaultWarden is already it's own thing code base wise, so, it likely won't effect the hosted portion of it at all.

The apps though, sounds like right now, it sounds like it won't make a difference, but, I think moving forwards it'd make sense to consider forking and making VW branded versions.

With that said, right now, the only reason you can choose your own domain is because BW allows you to self host their own product and VW just made their API respond the same way as BWs, so, as long as BW keeps allowing the self host option, I would imagine that there really isn't much they can do about VW other than starting to play games with their API, which would also impact their paying customers.