
# Internal tools on STACKIT

Compare documented Internal tools deployments on STACKIT, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/stackit/internal-tools/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: STACKIT organization and project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.stackit.cloud/products/runtime/kubernetes-engine/ (checked 2026-11-20).
- Network: Project-scoped cluster and application networking; review ingress and service exposure
- Identity and access: Project roles, service accounts and optional OIDC workload identity federation
- Installation guidance: Use the documented vendor-managed customer-cloud deployment or a separately supported installation path. STACKIT Kubernetes Engine supplies managed Kubernetes; platform availability alone does not establish application support.
- Guidance source: https://docs.stackit.cloud/products/runtime/kubernetes-engine/
- Guidance reviewed: 2026-11-17


### Service accounts

Grant project-scoped service-account roles for automation, protect private keys and prefer short-lived workload identity where supported. Vendor operating access must be reviewed separately from application deployment.
Source: https://docs.stackit.cloud/platform/access-and-identity/service-accounts/ (reviewed 2026-11-17).

The listings below have evidence for STACKIT. Read each cloud evidence note for the applicable package, edition and support qualifications.

1 listing.


## Mendix on Kubernetes

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

- Listing: https://launchinyourcloud.com/directory/mendix-private-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp, stackit
- Operating model: Customer-operated · vendor control plane
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: Helm / Kubernetes operator; Kubernetes manifests
- Architecture: Mendix Operator, application runtimes, database and file storage on the documented managed-Kubernetes providers.
- Operations: Customer operates the application runtime; the documented connected deployment also depends on the Mendix management portal and its configured access.
- Product website: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

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.

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

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.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

- stackit: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (checked 2026-11-19). 

Operating responsibility: 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. Source: https://docs.mendix.com/developerportal/deploy/private-cloud/ (checked 2026-11-20).


### Cloud deployment evidence

- Supported Clouds (aws, azure, gcp, stackit): https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- Supported Clouds: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/

- Private Cloud Deploy: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/

- Insurance Claims: https://www.mendix.com/industries/insurance/

- Outside-Cloud Licensing: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- Mendix Legal: https://www.mendix.com/legal/

- Mendix on K8s RN: https://docs.mendix.com/releasenotes/developer-portal/mendix-for-private-cloud/

### Licensing sources

- https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/

- https://www.mendix.com/legal/

### Infrastructure sources

- https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Application end-user federation on a compatible Mendix runtime; verify module dependencies and app configuration. Source: https://docs.mendix.com/appstore/modules/saml/ (reviewed 2026-11-20). Supporting source: OIDC module and supported runtime versions — https://docs.mendix.com/appstore/modules/oidc/.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Mendix on Kubernetes deployment workflow; operator, runtime and application releases are separate. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-deploy/ (reviewed 2026-11-20). Supporting source: Cluster and operator setup — https://docs.mendix.com/developerportal/deploy/private-cloud-cluster/.

- Minimum footprint / sizing: Documented. 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. Scope: One simple app baseline, excluding cluster overhead and HA/1-TB workload capacity. Source: https://docs.mendix.com/developerportal/deploy/private-cloud-supported-environments/ (reviewed 2026-11-20).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Mendix on Kubernetes; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.mendix.com/developerportal/deploy/licensing-apps-outside-mxcloud/ (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






