The whole point of a headless CMS is to not have to manage the CMS infrastructure. With Strapi, you would still need to manage the infrastructure yourself. This is actually called a "decoupled CMS".
Decoupling doesn't have anything to do with managing infrastructure. It means that the front end and the backend are communicating through an api, not a DB. This way you are not obliged to use the front end rendering of you don't want to. It's a special case of a headless CMS.
If Strapi started a hosted option, they would very much compete with your product. If your company goes under, customers have a lot fewer escape hatches than they do with open-source solutions.