You can choose to delegate the uncertain overheads to a company that relies (and specializes) on dealing with them. Or you can roll it yourself and add to your burden.
Code is not an asset, it's a liability. And I mean that from a pure responsibility standpoint, not just from a legal responsibility standpoint.
Sure, code is a liability. Having a dependence on on something outside your control is a liability. Those two have to be weighed against each other. I'm not against buying services on principle, I puy services from plenty of SaaS providers. I'm simply arguing that in this case the scales tip in the wrong direction for me, and likely a lot of other people like me.
Code is not an asset, it's a liability. And I mean that from a pure responsibility standpoint, not just from a legal responsibility standpoint.