Say hello to Mendix Portable Runtime: the modern way to deploy Mendix apps

If you’ve been building and running Mendix apps for a while, you know that deployment has always been a critical (and sometimes complex) part of the journey. Today, we’re excited to share that this is about to get a whole lot better.
We are introducing Mendix Portable Runtime: a modern, container-native deployment approach that simplifies how you package, distribute, and run your Mendix applications. And with it, we’re officially beginning the sunset of the Mendix CF Buildpack, Docker Buildpack, M2EE and Private Cloud / Mendix on Kubernetes Standalone.

A new era for Mendix deployment

The Mendix Buildpacks — both the Cloud Foundry (CF) Buildpack and the Docker Buildpack — or M2EE tool have served the community well. They were the backbone of self-hosted and custom deployments for years, and we’re proud of what they enabled. But technology evolves, and so does Mendix.
We are moving to Mendix Portable Runtime to embrace a modern, container-native approach that packages Mendix applications, making them more portable, flexible, and fully compatible with today’s cloud-native.

What is Mendix Portable Runtime?

Mendix Portable Runtime is a container-native approach to deploying Mendix applications. Instead of relying on buildpack scripts and platform-specific configurations, Mendix Portable Runtime packages your Mendix app as a standard OCI container image.
This means your app becomes a self-contained, portable unit that can run on:

• Kubernetes: the industry standard for container orchestration
• Docker: for local development and simpler environments
• Any OCI-compliant container runtime: giving you full flexibilit

The result? A deployment experience that feels right at home in the modern cloud-native ecosystem.

What makes Mendix Portable Runtime better?

We didn’t just build Mendix Portable Runtime to replace the Buildpacks, we built it to be genuinely better in every meaningful way.
Here’s what changes for you:

Simplicity first
Gone are the days of managing complex buildpack configurations and platform-specific quirks. With Mendix Portable Runtime, you build a container image and deploy it. That’s it. The workflow is clean, predictable, and easy to automate in your CI/CD pipeline.

Deploy anywhere
Because Mendix Portable Runtime produces a standard container image, you are no longer tied to a specific platform or runtime. Whether you’re running on-premises Kubernetes, a managed cloud service, or a local Docker environment, Mendix Portable Runtime works the same way everywhere.

Built to scale
Mendix Portable Runtime is designed with scalability in mind. Container images are immutable, versioned, and easy to replicate — making horizontal scaling, rollbacks, and blue-green deployments straightforward and reliable.

Ready for the future
Mendix Portable Runtime is the foundation for Mendix custom private deployments going forward. It fully supports Mendix 12 and all future versions, meaning your investment in migrating to Mendix Portable Runtime is an investment in staying current with the Mendix platform for years to come.

Familiar tools, better experience
Mendix Portable Runtime integrates naturally with the tools your DevOps teams already know and love — Docker, Kubernetes, Helm, and standard container registries. No proprietary tooling. No steep learning curve.

What happens to the Buildpacks?

The Mendix CF Buildpack and Docker Buildpack together with M2EE and Private Cloud / Mendix on Kubernetes Standalone are officially starting at the sunset by deprecating with the Mendix versions.
What this means for you:

• We will continue to support and update the Buildpacks, if necessary, including security vulnerability patches, for the current Mendix versions.
• The Mendix Buildpacks, M2EE and Private Cloud / Mendix on Kubernetes Standalone will stop supporting Mendix 12 and beyond.

If you are currently using either Buildpack, we encourage you to begin planning your migration now.
The good news? You have time, a clear path forward, and a team ready to support you.

How to get started with Mendix Portable Runtime

Getting started with Mendix Portable Runtime is straightforward. Here’s the high-level flow:

1. Build your app using Studio Pro or MxBuild: Mendix Portable Runtime compiles your Mendix app into a container image
2. Push to a container registry: store your image in Docker Hub, Azure Container Registry, AWS ECR, or any OCI-compatible registry (optional)
3. Deploy to your runtime: roll out your container image to Kubernetes, Docker, or your platform of choice

For full step-by-step instructions, visit the Mendix Portable Runtime Documentation.

We’re here every step of the way

We know that migrations take planning, and we want to make this one as smooth as possible. Here’s where you can get help:

• Mendix Portable Runtime Documentation: comprehensive guides and reference material
• Mendix Community Forum: connect with other developers making the same journey.

The future of isolated Mendix deployment is here

Mendix Portable Runtime is more than a replacement for the Buildpacks, M2EE and Private Cloud / Mendix on Kubernetes Standalone — it’s a leap forward for how Mendix applications are built, shipped, and run. It’s simpler, more powerful, and designed to grow with you.
Unlock Mendix’s full deployment flexibility: explore the wide range of deployment options to find the approach that fits your infrastructure, your team, and your goals.
We’re incredibly excited about this next chapter, and we can’t wait to see what you deploy.

Ready to get started? Explore Mendix Portable Runtime