this post was submitted on 30 Apr 2025
80 points (96.5% liked)

Selfhosted

61378 readers
373 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I am looking into password managers, as number of my accounts are increasing. Currently I am weighing two options:

  • Host Vaultwarden on a VPS, or
  • Use the free bitwarden service.

I want to know how they are in practical aspects.

While I am fine self-hosting many services, password managers seem to be one of the most critical services that should not admit downtime. I surely cannot keep it up, as I need to update it time to time.

On the other hand, using bitwarden might require some level of trust. How much should I trust the company to use the free service? How do I know if my passwords would be safe, not being exposed to the wide net?

I want to gauge pros and cons, are there aspects I missed? How are your opinions on this? If you are self-hosting vaultwarden, how do you manage the downtime? Thanks in advance!

you are viewing a single comment's thread
view the rest of the comments
[–] mbirth@lemmy.ml 4 points 1 year ago (2 children)

I’d throw in option 3: use a KeePass2 database, sync it using whatever sync tool you like (SyncThing, iCloud, NextCloud, WebDAV, …) and use compatible apps (KeepassXC, Strongbox, etc.)

[–] mhzawadi@lemmy.horwood.cloud 8 points 1 year ago (2 children)

I migrated from KeePass2 as the the DB would get out of sync and need to be merged back together. Thats why I moved to Vaultwarden, I like having my data on my own stuff

[–] mbirth@lemmy.ml 1 points 1 year ago

I’m using Strongbox on iOS and macOS with iCloud Sync and never had any merge issue. Well, maybe once when I deliberately edited the same entry on two different devices. But during normal use, the sync and merge works great.

[–] lka1988@lemmy.dbzer0.com 1 points 1 year ago* (last edited 1 year ago)

I keep seeing people mentioning Syncthing with KeePass... I use both, but not together, between 3-4 different devices. I have a central Syncthing server to which all devices sync everything, but my KeePass database (keyfile & password protected is stored on Google Drive, in a G Suite Workspace account that I pay for. The keyfile is stored individually on each device that needs it, with a printed out copy (with instructions!) as a backup.

Would my keypass database survive Syncthing the way I have it setup?

[–] coaxil@lemm.ee 2 points 1 year ago

I roll it this way, been like this for years and years, fine for my needs