Published version update in app stores
community.bitwarden.com
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...

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
  • KssioAug@piefed.zipEnglish
    2·
    3 hours ago

    I had a feeling it was going to happen at any time. Back to KeePass it is! I was already considering this anyway, so all I needed was a little push.

    • Andrew Zabar@lemmy.worldEnglish
      7·
      1 day ago

      Everything gets enshittified because when push comes to shove, every human will sell out in this economic mass-extinction.

  • Andrew Zabar@lemmy.worldEnglish
    7·
    1 day ago

    So how does this affect someone like my situation I have the software installed on iOS and a few androids and a Linux. I have them all syncing using Bitwarden’s server (I know, I’m gonna change to self-hosted eventually). Do I have to find a new platform for my passwords?

    • x1gma@lemmy.worldEnglish
      82·
      23 hours ago

      It doesn’t, since you’re not repackaging or reselling. It’s classical FUD as it is with any other license change in popular software. There already is a subscription. You already need the subscription for features even if you self host. The moment bitwarden pulls anything too greedy or suspicious there will be hard forks, and since vaultwarden already exists as a drop-in replacement for the official server, the API is well-known, those forks would be a massive problem for bitwarden as a company. Realistically, the single question is the same as it’s been before the announcement: do you want to pay for comfort and to fund further official development, then go for bitwarden, or to use vaultwarden and self host it, and get more free features on your infra. OSS projects can pull fucky shit too, and die just like any other commercial product. You gotta trust someone.

      • Andrew Zabar@lemmy.worldEnglish
        3·
        16 hours ago

        Preaching to the choir buddy, I am a FOSS fan and pretty much everything I run is free and open-source. Thanks for the info, I appreciate it.