Not sure how easy self-hosting those are, but any paid-for and/or online offering by a third party is useless. This should have been clear long ago, but the LastPass breach should have made it obvious.
No system is perfect. You're making a trade off by self-hosting but at least when something goes wrong you know who to blame and what to improve. When something goes wrong in someone else's environment you're lucky to even know what went wrong, and you have no one to hold accountable.
So it's not IF something goes wrong, it's WHEN something goes wrong. Going around thinking IF something goes wrong is delusional, even if you end up being lucky and right.
You're right. I'm sure their security design is 100% bulletproof and none of my sensitive data will ever be leaked. And even if it were somehow possible for it to be leaked, I'm also sure the company would be completely forthcoming as quickly as possible.
A system which literally never sends my password information to any computers controlled by 1Password seems better than the LastPass nonsense, and more to the point, seems at least as secure as anything I would create. While LastPass was breached many times over the last few years, 1Password has never been breached.
Your sarcasm isn't helpful, and serves only to falsely conflate the insecure design and horrible history of LastPass with the best-in-class 1Password. Nothing is ever 100%, but 1Password is closer than anything else I know about, including most one-off systems used by people who don't use password managers.
Self-hosting Bitwarden with the open source Rust re-implementation of the server (vaultwarden) seems like a good option. I've been looking into setting it up for my company.
Or the official open source server, which has the potential to get support from Bitwarden if it gets to it. It's much heavier though, with SQL Server and similar, but vastly more enterprisey.