this post was submitted on 02 May 2026
41 points (63.8% liked)

Technology

84302 readers
7576 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
41
I Do Not Recommend Bitwarden (xn--gckvb8fzb.com)
submitted 1 day ago* (last edited 19 hours ago) by mesamunefire@piefed.social to c/technology@lemmy.world
35 comments fedilink hide all child comments
 

A review of my experience with Bitwarden after several years of self-hosting it, and why I decided to move away from the password manager.

Note: this is not my article.

you are viewing a single comment's thread
view the rest of the comments
[–] turdas@suppo.fi 1 points 21 hours ago

Do you mean Vaultwarden? AFAICS they do not "settle" on it, but they do argue that it is much lighter in almost every respect. And since it is Bitwarden compatible the comparison is valid.

I don't know which one I mean, because OP never says which SaaS password manager they switch to, they simply say they switch to a proprietary SaaS password manager:

For group A I’m going with a SaaS password manager that offers proper vault sharing, integrates with the tools clients actually use (SSO, browser extensions on corporate machines, audit logs), and takes the hosting burden off my plate. The platform is proprietary, which I would normally not be thrilled about, but given that the scope of this group is client work only, I’m accepting the trade-off.