Components of the Mendix Stack

Last modified: March 9, 2026

Introduction

These are the components of the Mendix stack.
You can read an extensive description of the Mendix architecture in the Evaluation Guide.

Database, File Storage, and Network

The database component includes the database service and the creation, storage, downloading, uploading, and restoration of backups. The file storage component refers to the file storage service and the creation, storage, downloading, uploading, and restoration of backups. The network component consists of the connection between the front-facing web server and the application, between the application and an external endpoint.

Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated.

Infrastructure

The infrastructure component includes all web servers, runtime servers, and database servers, with their Operating Systems and configurations.

Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated.

Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.

Container Runtime Platform

The container runtime platform refers to the platform for managing, creating, destroying, and scaling of runtime containers. In Mendix Cloud and Mendix Cloud Dedicated, Kubernetes is used.

Mendix Support can analyze this component if your app is running on Mendix Cloud or Mendix Cloud Dedicated.

Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers. If it is running on SAP BTP instead, the selected third party can analyze this component.

Buildpack, m2ee, and Service Console

The Mendix buildpacks for Cloud Foundry and Docker are available in GitHub repositories. The documentation for the buildpacks and m2ee tools is contained within these GitHub repositories. Because they are released under an open-source license, the code can be inspected, and the functionality and options can be understood by customers who wish to use these buildpacks.

If you want to run Mendix apps on a Unix-like server, you will need the m2ee tools, available on GitHub. Read more about installing on systems running Unix-like operating systems in Linux Deployment.

Mendix Support can analyze these components if your app is running on Mendix Cloud or Mendix Cloud Dedicated. Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.

Because Mendix has no control over the context in which the buildpack or m2ee tools are run outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently from the context in which you are using it.

If you require additional features or other changes in a buildpack or m2ee tools, you can submit a Pull Request, create an Issue in the GitHub repository, or contact Mendix Support.

If you want to run Mendix apps on a Windows server, you will need the Windows Service. The release notes and installation manual can be found in the Windows Service release notes. Read more about installing on systems running Windows operating systems in Microsoft Windows.

For additional features or other changes in the Windows Service, contact Mendix Support.

Application Operation

The application operation component is used for stopping and starting environments and configuring constants, scheduled events, and runtime settings.

Mendix Support can analyze this component if your app is running on Mendix Cloud, Mendix Cloud Dedicated, Mendix on Kubernetes Connected, or SAP BTP through the Mendix Portal. Mendix is responsible for setting up and maintaining the component, as well as applying default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.

Logs and Metrics

The logs component handles viewing and downloading application log files. The metrics component refers to viewing application metrics.

Mendix Support can analyze these components if your app is running on Mendix Cloud or Mendix Cloud Dedicated. Mendix is responsible for setting up and maintaining the component, as well as applying the default configuration. This component cannot be customized or optimized for individual customers or applications outside the supported configuration options available to our customers.

Deployment Pipeline

The deployment pipeline handles creating and deploying deployment packages. Read more about deployment options in Deploying Apps.

Mendix Support can analyze this component if your app is running on Mendix Cloud, Mendix Cloud Dedicated, Mendix on Kubernetes Connected, or SAP BTP through the Mendix Portal.

Runtime

The runtime component includes the Mendix Runtime and all of its supported features. Please read all about the Mendix Runtime in Mendix Runtime.

Mendix Support needs application logs to analyze this component. Because Mendix has no control over the context in which the runtime is run, outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently from the context in which you are using it.

Marketplace Components

Platform-supported Marketplace content refers to all Marketplace content marked as platform-supported in the Mendix Marketplace. Community-supported Marketplace content includes all Marketplace content not marked as platform-supported in the Mendix Marketplace.

For details about the levels of Support for Marketplace components, refer to the Marketplace Content Support section in Marketplace Overview.

Mendix Support needs application logs to analyze these components. Because Mendix has no control over the context in which the Marketplace content is run outside of Mendix Cloud and Mendix Cloud Dedicated, you will have to demonstrate that the bug is in the supported component by showing the behavior independently of the context in which you are using it.

Application

This includes the implementation and configuration of features, as well as the data and files in the Mendix app itself.

These components are not accessible to Mendix Support, and issues in the application are outside the scope of Mendix Support, although we will gladly assist with any questions.