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
  • @NGC2346@sh.itjust.worksEnglish
    3•2 hours ago

    If you are on Lemmy, theres very high probability that you also have the technical abilities required to self host Vaultwarden and stop relying on a greedy company for your most critical aspect.

    • ImpulseDrive42English
      1•1 hour ago

      I have Vaultwarden, it works with the web app and browser extensions. But is there a vaultwarden specific android app? I know technically I can use the Bitwarden app. But sometimes they update the Bitwarden app too fast for all the changes to translate into Vaultwarden and then im kinda forced to use the web app.

      The web app is just a minor inconvenience to me so I continue to use it. Just wondering if there is an easier Vaultwarden specific solution for android.

  • Jubei KibagamiEnglish
    3•2 hours ago

    Fantastic. I’m tired of having to change password managers. DashLane, Keepass, LastPass, etc., they all end up shooting their own foot somehow.

  • RoseEnglish
    13•8 hours ago

    When Bitwarden got a meh “refresh” of the user interface and started vibe coding stuff (I’m not some super hard-line anti-AI person, but dammit, you absolutely should not vibe code security-critical apps), I switched to KeePassX. It was like coming back home! I used to use KeePass and KeePass 2, switched to Bitwarden for a long while, and while it was neat, KeePassX is just neater. (Doesn’t have cloud sync, but syncing the vault files with LocalSend is easy enough.)

  • @AppleMango@lemmy.worldEnglish
    15•9 hours ago

    I think all of us can just using Vaultwarden, it seems to fix all the problems that are there even in the old free version of Bitwarden.

  • @ture@lemmy.mlEnglish
    45•11 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
      31•11 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
        35•9 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
        2•9 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.

  • @dmtalon@lemmy.worldEnglish
    17•11 hours ago

    Sigh… I hope this isn’t the first move of enshitifying bitwarden. I read the comments/replies and hope this is benign but I’m now nervous

    • scytaleEnglish
      36•9 hours ago

      The first move was when they hired a CEO who comes from private equity. This is the second move.

    • Mike WooskeyEnglish
      32•11 hours ago

      I think it is the next move (not the first) in enshittifying bitwarden. I think the first move was the leadership change announced in May.

  • @woelkchen@lemmy.worldEnglish
    10•11 hours ago

    App store EULAs and GPLv3 frequently clash. This change only affects the app store binary releases.

      • @woelkchen@lemmy.worldEnglish
        0•3 hours ago

        So, 99% of users.

        How? It’s not like the source code if no longer under GPL, it’s just that this specific compiled binary is under a different license but it doesn’t change anything for anyone in real life.