Private-cloud Mendix operations, without pretending it is automatic.
For IT teams asked to take Mendix off a public host, or to run many client instances, without staffing a Kubernetes practice for each one.
A supported operations path. Not a Mendix replacement.
Use this with the security pack and the one-app pilot. Do not treat a template repository as a production architecture.
The supported path
Low-Ops has a public Mendix app template and customers already running Mendix in a private cloud. That is the evidenced starting point — not a claim that every Mendix runtime option is certified here.
Why IT usually blocks it
Public Mendix Cloud is fast until data residency, client isolation or a white-label topology shows up. Rolling your own Kubernetes for each instance is the other extreme. Low-Ops is the operations layer in between.
What the platform takes
Hosting the app, environments, pipelines, backups, SSO at the platform edge, and a portal record of who deployed what. Spinning up another instance is a platform action, not a new cluster project.
What Mendix and the app still own
The model, microflows, app-level security, and Mendix platform licences. Low-Ops does not replace Mendix Cloud content management or your Mendix licensing with Mendix itself.
Working example
Efficient Group hosts Mendix in its own cloud and creates white-label client instances from the portal. Read the case study for the named quotes and the limits of what we claim.
Limitations
Single-node Community is not this path. Production Mendix needs a Kubernetes-compatible environment, identity, and a tested restore. Implementation partners such as Comotion and Lowcode Labs already deliver this motion.