I like to support devs who makes great products, excellent ones like bitwarden. Otherwise they will go away and we will be left with big tech products only. Because I don’t think people like to make excellent products and still don’t see a dime in their pocket.
I like to support devs, too - But I don’t like being forced into paying for access to features already present in software that is running on my own hardware. The code is already on my machine, I should be able to run it.
That’s my biggest complaint about Bitwarden - I want to share passwords with my wife, and they want to charge me money for that even when I host it myself.
It is open source - but the server essentially locks you out of various functionality unless you create an account with Bitwarden and provide a valid subscription token.
Sure, you can fork it and excise that code from it… but that’s too laborious and potentially error-prone, imho.
If I were to selfhost bitwarden again, I’d go with Vaultwarden, which claims to be fully compatible and has no such requirements.
Specificly VaultWarden. Gives you all the premium features of Bitwarden for free!
I like to support devs who makes great products, excellent ones like bitwarden. Otherwise they will go away and we will be left with big tech products only. Because I don’t think people like to make excellent products and still don’t see a dime in their pocket.
I like to support devs, too - But I don’t like being forced into paying for access to features already present in software that is running on my own hardware. The code is already on my machine, I should be able to run it.
That’s my biggest complaint about Bitwarden - I want to share passwords with my wife, and they want to charge me money for that even when I host it myself.
Is that really how it works? I thought it was all open source software? If it is I don’t see how you can be required to pay if you host it yourself?
It is open source - but the server essentially locks you out of various functionality unless you create an account with Bitwarden and provide a valid subscription token.
Sure, you can fork it and excise that code from it… but that’s too laborious and potentially error-prone, imho.
If I were to selfhost bitwarden again, I’d go with Vaultwarden, which claims to be fully compatible and has no such requirements.