[rglullis]

That's the other part that breaks my lizard brain.

We are talking about $5k/month vs $500. If the UX of the FOSS version is lacking, pay for the closed version BUT throw $1000/month on the direction of the FOSS developers until the issues are mitigated and they satisfy your requirements. I can bet that in less than a year you'd be able to make a switch and the investment would pay itself.

[rrdharan]

> BUT throw $1000/month on the direction of the FOSS developers until the issues are mitigated and they satisfy your requirements

This is not at all an easy thing to guarantee even if you’re willing to spend the money. The FOSS developers might not be interested in doing this work (even for pay) nor have UX staff.

[rglullis]

Do you have any idea how much "developer power" you can buy with $1000/month, if you just look in the right places?

So many talented people working for that money or less in São Paulo, Buenos Aires or Hanoi, it would be worth it to give it a shot even if they just worked part-time.

[rrdharan]

Right, but then you need to trust them to maintain a fork of vaultwarden or hope that vaultwarden accepts their patches.

[rglullis]

Third option: the team looks at the work from someone who is outside and bring them to do the things that the team is not interested in doing.

In all three cases, though, it sends a signal that there is demand for the changes. This works as both validation for the developers (our users wants this so much they are paying someone else to do it) and also for other companies (oh, why should we be paying this much to a closed-source service if we can pay a fraction of the price to get a reasonably-well-supported open source version?)