3 ms·
Probably because you could self-host your own password manager for free with serverless solutions (low maintenance). Part of the migration away from LastPass.
by lukevp 4y ago
Probably because you could self-host your own password manager for free with serverless solutions (low maintenance). Part of the migration away from LastPass.
Personally I just run it on a DigitalOcean droplet with several other containers, but the maintenance is a bit higher and it’s not free. You can get free micro VMs though if you want, from AWS or Oracle Cloud or whatever, but you’ll still have to pay for it in maintenance burden.
I would guess that you could host vaultwarden in a fargate container or a lambda and pay very little for it… use EBS to store a persistent SQLite DB. it seems to not poll the server too heavily and the performance wouldn’t be that sensitive. It’s in rust so I’m guessing the startup time is pretty fast.
- e44858 4y agoFor me self-hosting makes the most sense when it’s on my own hardware, because the privacy benefits of owning my data make up for the lost convenience. If you want a cloud-based deployment, wouldn’t it make more sense to let BitWarden host it for you?
- iakov 4y agoEspecially given the price of Bitwarden paid cloud offering - 10 bucks per year!
- lukevp 4y agoIf bitwarden is compromised, I won’t be impacted. My single server is much less likely to be compromised because the payoff of compromising it is so small. The password vault is encrypted based on your master password, so it isn’t like the cloud provider has all your passwords in plain text.
- cassianoleal 4y agoThanks. None of this was obvious from the submission, but you could be right. I tend to agree with the sibling commenter though, that self-hosting something as sensitive as a password manager tends to have diminishing returns when you self-host it on a third-party computer and network, free or paid.