In the (future) case of a localized erpnext, the maintaining partner - in order to serve the SaaS segment would have to spinup and maintain it’s own cloud platform.
Definitly, a good partner consists in good implementation services and good local funcional and framework knowledge, infrastructure questions are not his unique selling position.
As he does not dispose of such capabilities, for effectivley doing his job, he would require abstraction and ease of use.
Set up a standard way of doing which makes ife of partners a lot easier:
- Expose single node behaviour to the partner through mesosphere as a cloud agnostic (!) Data Center Operating System
- Leverage the advantages of containerized applications by providing optimized and deterministc dockerimages for production (see interesting articles 1 & 2) and development workflows
- Make use of mesosphere native docker support and spin up client images from a partner private registry, if the client requieres a private cluster - say 2 app-dockers