Mendix on Kubernetes

Commercial low-code application runtime operated in customer Kubernetes infrastructure.

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Helm / Kubernetes operator; Kubernetes manifests

    External vendor control plane

  2. Operated by

    Your team

    Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Supported Clouds ↗ · Source checked 2026-11-19

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Supported Clouds ↗ · Source checked 2026-11-19

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Supported Clouds ↗ · Source checked 2026-11-19

  • STACKIT: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Supported Clouds ↗ · Source checked 2026-11-19

In the selected Connected mode the customer supplies and operates the Kubernetes runtime, database, storage and backups. The Mendix Portal controls deployments through an in-cluster agent. This is not a vendor-operated application service.

Operating responsibility source ↗ · Checked 2026-11-20

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodHelm / Kubernetes operator; Kubernetes manifests
InfrastructureServers / containers
Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelCommercial Only
Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
LicenseCommercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

4 of 12 fields researched (33%) · 4 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

Mendix documents SAML and OIDC modules for end-users of deployed apps, with module/runtime compatibility and app-level configuration. The SAML guide explicitly addresses apps outside Mendix Cloud and requires external file storage. This is separate from developer-portal or Private Mendix Platform login.

Application end-user federation on a compatible Mendix runtime; verify module dependencies and app configuration · Source ↗ · OIDC module and supported runtime versions ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The Kubernetes deployment guides register a cluster/namespace, install the Mendix Operator and deploy app environments from the Mendix Portal or Kubernetes custom resources. Database, file storage, registry, network access and licensed runtime configuration remain deployment inputs.

Mendix on Kubernetes deployment workflow; operator, runtime and application releases are separate · Source ↗ · Cluster and operator setup ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The supported-provider guide requires at least 2 CPU cores, 2 GB memory and 3 GB ephemeral storage available on a node for one simple app, excluding Kubernetes core components. Production databases, file storage, image building and multiple replicas need additional sizing; experimental ARM64 support is limited to non-production Connected Mode.

One simple app baseline, excluding cluster overhead and HA/1-TB workload capacity · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Mendix on Kubernetes; software terms only, excluding cloud charges, labour and separately licensed services · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (8 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.
Release snapshot / cadence
Not researched Supply a public source.

Scope & considerations

The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.

Category fit

Internal tools
Commercial low-code application runtime operated in customer Kubernetes infrastructure.
Workflow automation
Commercial low-code application runtime operated in customer Kubernetes infrastructure.

Compare within Internal tools

  • Appsmith Self-HostedBuild internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Budibase Self-HostedBuild operational apps and automations on customer-hosted infrastructure.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • CortezaLow-code platform for business records, workflows and configurable CRM applications.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Grist Self-HostedRelational spreadsheet platform for collaborative business data and configurable operational applications.
    • AWS
    • Azure
    Customer-operated · Open Source / Open Core
  • NocoDB Self-HostedSpreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Railway
    Customer-operated · Source Available

Showing 8 of 10 other listings in Internal tools. These products address related workflows; read their category-fit notes before comparing scope. See all of Internal tools →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Supported Clouds ↗ · AWS, Azure, Google Cloud, STACKIT

      Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers. The selected connected deployment registers the cluster with the external Mendix Portal control plane. A customer cluster is not a packaged insurance-claims application. Runtime licences, operator versions and application versions have different lifecycles; standalone modes need their own review.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory