I would avoid a support nightmare if you can't sell a maintenance/support contract for the backend part and try to avoid deploying a CMS at all. I would sugges

I would avoid a support nightmare if you can't sell a maintenance/support contract for the backend part and try to avoid deploying a CMS at all. I would suggest you look at CaaS solution like Contentful, Prismic.io or similar which would provide the editing interface as a service and simply expose the content through an API for your front-end code to use. No issue with having to update and maintain the CMS, no issue with scaling, less security concerns, etc... If you are not in the business of hosting CMS, it's clearly the best solution for you.