Skip to content

Clarify Mendix on Kubernetes subscription requirement after Operator license removal #11615

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MXClyde wants to merge 3 commits into
base: development
Choose a base branch
from
+4 −6
Open

Clarify Mendix on Kubernetes subscription requirement after Operator license removal #11615

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9c18a19
Clarify that a Mendix on Kubernetes subscription is still required af…
MXClyde Jul 27, 2026
6f02e94
Update _index.md
katarzyna-koltun-mx Jul 27, 2026
3513cfe
Update _index.md
katarzyna-koltun-mx Jul 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions content/en/docs/deployment/private-cloud/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Your organization may have a requirement to use a private cloud, perhaps as part

You can use Mendix on Kubernetes with the *connected* option to keep the simplicity of one-click deployments from the Mendix Portal, or utilize the *standalone* Mendix Operator to deploy Mendix apps through your own DevOps process, which is particularly useful for private clouds with an *air-gap* isolating them from the internet. See [Connected and Standalone Clusters](#connected-standalone), below, for more information.

Please see [Supported Providers](/developerportal/deploy/private-cloud-supported-environments/) for a list of platforms supported by Mendix on Kubernetes.
For a list of platforms supported by Mendix on Kubernetes, see [Supported Providers](/developerportal/deploy/private-cloud-supported-environments/).

There are two steps required to achieve this, listed below.

Expand Down Expand Up @@ -105,12 +105,10 @@ This percentage can be adjusted by providing a custom value in Custom JVM Option
### Operator License

{{% alert color="info" %}}
Mendix Operator versions older than 2.23.0 require an Operator licence. Starting from Operator version 2.23.0, Operator licenses are no longer needed.

A valid subscription and support contract is still necessary to be receive technical support.
Mendix Operator versions older than 2.23.0 require a separate Operator license key. Starting from Operator version 2.23.0, this separate license key is no longer needed. This was a technical change only. A valid Mendix on Kubernetes subscription and support contract is still required to use the Mendix Operator, regardless of Operator version.
{{% /alert %}}

Mendix on Kubernetes is a premium offering from Mendix, and you will need an additional license to use it for your applications. This **Operator license** allows you to manage Mendix apps in your cluster through the Mendix Operator and, optionally, the Mendix Gateway Agent.
Mendix on Kubernetes is a premium offering from Mendix, and requires a valid subscription to use it for your applications. If you are running Mendix Operator versions older than 2.23.0, you also need a separate Operator license. This license allows you to manage Mendix apps in your cluster through the Mendix Operator and, optionally, the Mendix Gateway Agent.

You need one license for each namespace you want to manage.

Expand All @@ -137,7 +135,7 @@ You can run the Mendix Operator in trial mode for evaluation purposes. When the

### Runtime License

A runtime license per environment is required. In addition to that, the Operator license is independent of a Mendix Runtime license. The Mendix Runtime license removes [trial restrictions](/developerportal/deploy/licensing-apps-outside-mxcloud/) from a Mendix App itself. You need both types of licenses to manage and run an application through Mendix on Kubernetes.
A runtime license per environment is required. In addition to that, the Mendix Runtime license is independent of the Operator license. The Mendix Runtime license removes [trial restrictions](/developerportal/deploy/licensing-apps-outside-mxcloud/) from a Mendix app. You need both types of licenses to manage and run an application through Mendix on Kubernetes.

You can request a Runtime license by doing the following:

Expand Down