If you only care about convenience, you shouldn't be self-hosting - what if your server goes down? Much better to abstract this away and let someone else take care of it.
If you only care about security, you don't want anyone else's prying eyes anywhere near your recursively-encrypted secrets; self-host on a server that is airgapped from any publicly accessible networks.
Even if I give up convenience for security, I may not be a seasoned DevOps guy like the one who is payed good salary to do that 24x7. So it turns out that self-hosting is not for everybody. Small mistakes in configuration can lead to entire infra getting compromised.
If you only care about convenience, you shouldn't be self-hosting - what if your server goes down? Much better to abstract this away and let someone else take care of it.
If you only care about security, you don't want anyone else's prying eyes anywhere near your recursively-encrypted secrets; self-host on a server that is airgapped from any publicly accessible networks.
Which of these do you care about more?