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
  • 1984@lemmy.today
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    1
    ·
    8 hours ago

    There is no way I’m self hosting something this important… So now I’m not sure what to do actually.

    • sonstwas@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      8
      ·
      4 hours ago

      That’s why I’m just using KeePass. It’s just an encrypted file that you can store on whatever storage you want and sync with existing solutions like Syncthing etc.

      Yes it’s a bit finicky when you edit the file on multiple devices before they’ve synced but it works very well for me…

    • ominous ocelot@leminal.space
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 hours ago

      If self hosting is not an option. Ideas that come to mind:

      Evaluate what it is worth to you and maybe pay for it, if they offer enough worth to you and it is affordable.

      Then there are people who host it and provide it to others. Together with other apps, as a suite. Maybe that’s an option. But I suppose, donating or paying is expected here, too.

      Or switch to another solution. Preferably one with an import feature.