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...

cross-posted from: https://thelemmy.club/post/57178743

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
  • ture@lemmy.mlEnglish
    49·
    15 hours ago

    That’s quite the disappointment. Probably need to prepare to switch away from bitwarden or at least research options for open source clients for my vaultwarden backend.

    • superglue@lemmy.dbzer0.comEnglish
      32·
      15 hours ago

      Someone can correct me, but this change seems to be targeting people who are repackaging bitwarden and selling it. It does feel like we are trending the wrong direction though.

      • ture@lemmy.mlEnglish
        39·
        13 hours ago

        If you read their announcement carefully you’ll find things like

        All current features are available in both versions

        Which strongly implies that the different versions will start to diverge over time. Then at one point they will just be like maah it’s not worth putting more work into the open source thing, we’ll focus on building new cool features yada yada yada. And this is how all the open to partly open to closed source rug pulls worked in the last years.

        (If you want to do this the worst way possible like MinIO you also squash / delete the Git history the moment you announce you’re only working on closed source)

      • ture@lemmy.mlEnglish
        3·
        13 hours ago

        Before Bitwarden / Vaultwarden I went with Keepass (it was some fork don’t remember the exact name KeepassXC probably) synced via Nextcloud. It’s not as convenient as Bitwarden plus at least back then it didn’t support passkeys. So yeah, I don’t know what is actually out there. Honestly I don’t think it’s super urgent to start hunting for alternatives but probably we should have at least some ideas in case the Bitwarden team does some weird moves.