System Requirements

Last modified: July 2, 2025

Introduction

This document presents the system requirements for the various parts of the Mendix Platform.

Mendix Studio Pro

Mendix Studio Pro has the requirements listed in the following sections.

Software Specifications

Mendix Studio Pro 11 is supported on 64-bit versions of Windows 10 release 1809 and above; this also includes Windows 11. We support running on Windows locally, or locally virtualized.

Mendix Studio Pro 11 can run in beta mode on an ARM Mac and Intel Mac running macOS Sonoma 14.0 and above. For information on known limitation, see the Known Limitations for Mac section below.

While Studio Pro on Mac is in public beta, Mendix can only verify support for the latest macOS version available. Support for earlier versions is not guaranteed and it is best to update macOS to the newest version when using Studio Pro.

Administrator rights are required to install Mendix Studio Pro on Mac (Beta).

Studio Pro 11 can run on the M series Apple Silicon Mac using Parallels 17 and Windows 11. It can also run on Apple Mac using Parallels.

If you were using Parallels and enabled port forwarding, but then upgraded and would like to use Studio Pro on Mac, make sure to quit Parallels to be able to sign in to Studio Pro.

The following frameworks are required. They will be installed automatically by the Studio Pro installer, if necessary:

Microsoft .NET Desktop Runtime 8.0.x (x64) and all applicable Windows security patches
Microsoft Visual C++ 2019 Redistributable Package (x64)
A Java Developer Kit (JDK) version 11, 17, or 21 - if not yet installed on your machine, Mendix will install ‘Eclipse Temurin JDK 21 (x64 or ARM64)’
Gradle version 8.5 or above - if Gradle is not yet installed on your machine, Mendix will install Gradle version 8.5
Git for Windows (x64) version 2.48.1 or above (for more information, see the Prerequisites section in Installing Mendix Studio Pro)
Mendix Native Mobile Builder
Microsoft Edge WebView2 Evergreen Runtime (x64)

When you are running Studio Pro on a Parallels virtual machine on an ARM64 device (for example, an M1 Mac), you need the following dependencies in addition to the x64 version listed above:

Microsoft .NET Desktop Runtime 8.0.x (ARM64)
Microsoft Edge WebView2 Evergreen Runtime (ARM64)

You can choose which JDK is used for building and running locally via the Edit > Preferences menu item in Studio Pro.

Known Limitations for Mac

These are the known limitations for Mac:

No native mobile support
No support for document templates
Start from spreadsheet cannot be used at this time
If you have already installed JDK previously, it may not be picked up properly during installation. You can either configure this manually or remove all references to JDK and run the installer again.

Hardware Specifications

Mendix Studio Pro will run on any machine which can run the minimum requirements for running Windows 10 64-bit, with the following additional requirements:

Disk Space – Studio Pro requires 2GB disk space to install, and each app you create will vary in size depending on the functionality, but will take a minimum of around 150MB
RAM – 8GB
Display Resolution – 1080p (1920x1080)

Mendix Studio Pro on Mac (Beta) runs on any machine compatible with macOS Sonoma

Firewall Settings

Studio Pro needs access to the following URLs in order to work. If your firewall is blocking these, you will need to safelist them:

*.mendix.com
*.mendixcloud.com
*.teamserver.sprintr.com
*.api.mendix.com

If you have set up managed dependencies and are working behind a firewall or using a proxy, see the Proxy Settings section of Managed Dependencies for advice on what you need to do to allow the managed dependencies to work.

To run a Mendix app, Mendix Studio Pro uses the following ports by default. If your firewall is blocking these, you will need to open them:

8080 – runtime port
8083 – mobile packager
8090 – admin port
8100 – sign-in port

For more information on ports and modifying Studio Pro’s default ports, see Configurations and the Troubleshooting Common Mobile Issues section of Native App Prerequisites and Troubleshooting.

For information on how to ensure the smooth operation of Mendix AI Assistance (Maia), see the Network Configuration Requirements section in Mendix AI Assistance (Maia).

File Comparison

Comparing files on disk with the original is currently not supported on macOS.

By default, Studio Pro points to an executable shipped with TortoiseGit for file comparison. To customize this, navigate to Preferences > Version control > General > File comparison > Executable and choose your preferred tool.

The default path for the binary when installing Studio Pro on a new device is C:\Program Files\TortoiseGit\bin\TortoiseGitMerge.exe.

You can download the latest version of TortoiseGitMerge from the TortoiseGit website.

File Locations

For active development and running your application locally, your app folder should be on a local drive (such as C:) or a network folder that has been mapped to a Windows drive letter.

Supported Git Service Providers

This section describes Git service providers when you are setting up your own Git repo. For information about Mendix Team Server (which is implemented using Git), see the Team Server section below.

Git service providers have size limitations related to commits and repositories.

Studio Pro does not support Large File Storage (LFS) for any provider.

You can find a list of known limitations below, however, we advise you to check the most up-to-date limitations on respective web sites before considering using a certain service provider.

Vendor	Repository Size Limit	Push Limit	Non-LFS File Size Limit	LFS File Size Limit
GitHub	Warnings on 5 GB, 100 GB theoretical limit	Information n/a	100 MB¹ (warning 50 MB)	5 GB
GitLab	5 GB (free) and 250 GB (enterprise)	5 GB	None	5 GB
Azure Repos	250 GB	5 GB	None	50 GB
Bitbucket	4 GB	3.5 GB	None	10 + 100 GB

¹ You will not be able to work with GitHub, and other providers with a file size limitation, if your .mpr file exceeds the limit.

Azure Repos and Azure DevOps Server

We support both Microsoft’s Azure Repos hosted Git service, and Azure DevOps Server (former Team Foundation Server) which is an on-premises solution for hosting your Git repos on private infrastructure.

To get a PAT for your user account, see the Use personal access tokens instructions in the Microsoft documentation.

You need Code (full) permission for your token.

GitHub

We support GitHub’s hosting solutions, including the free GitHub.com cloud-hosted service and GitHub Enterprise, both hosted (Enterprise Cloud) and on-premises (Enterprise Server).

To get a PAT for your user account, see the Creating a personal access token instructions in the GitHub documentation.

You need repo permissions for your token.

GitLab

We support all tiers of GitLab’s service, including GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition.

To get a PAT for your user account, see the Personal access tokens instructions in the GitLab documentation.

You need write_repository permission for the token.

Bitbucket

We support all tiers of Atlassian’s Bitbucket service, including Bitbucket.org, Bitbucket Server, and Bitbucket Data Center on-premises solutions.

On Bitbucket.org, the personal access token are called app passwords.

To set up an App Password for your Bitbucket.org account, see the App passwords instructions.

Bitbucket Server and Bitbucket Data Center, on the other hand, still use the term “personal access token.” To set up a personal access token, see the Personal access tokens instructions.

In both cases you need repository write permission.

Graphics Card

If you are using the Intel® UHD Graphics 630 graphics processor, please ensure that you are using driver version 27.20.100.9664 or above.

Team Server

The Team Server is implemented using Git, and Studio Pro uses the HTTPS protocol to communicate with that server. To access the Team Server from within Studio Pro, the network at your location needs the following settings:

The HTTPS port (TCP 443) needs to be open
The HTTP port (TCP 80) needs to be open
WebDAV (verbs within the HTTP protocol) needs to be enabled on the proxy server (if any)

Cloud Foundry

The Mendix Cloud Foundry buildpack supports Cloud Foundry versions v9 and above.

Docker

The Mendix Docker buildpack supports Docker version 18.09.0 and above.

Kubernetes

The Mendix Docker buildpack supports the following Kubernetes versions:

Kubernetes version v1.12 and above
Red Hat OpenShift v3.11 and v4.2 and above

Server

Operating System

Microsoft Windows Server 2012 and above
Linux: Debian 10 (Buster)

Web Server

Microsoft Internet Information Services 8 and above
Nginx
Apache

Java

When running Mendix on a server, you will need Java Runtime Environment 21 (JRE). To download an Eclipse Temurin OpenJDK distribution from Adoptium, see Eclipse Temurin™ Latest Releases. To download a commercial Oracle distribution, see Java SE Downloads.

Databases

Mendix tries to support the most recent and patched database server versions from database vendors. We aim to add support for a new vendor version two minor Mendix versions after the vendor has released it. Dropping support for a database will be announced in the release notes at the date the vendor drops support. We will drop support two minor Mendix versions later.

Current support:

MariaDB: 10.4, 10.5, 10.6, 10.11, 11.4
Microsoft SQL Server: 2019, 2022
Azure SQL: v12 compatibility mode 140 or higher
MySQL: 8.0, 8.4
Oracle Database: 19, 21c
PostgreSQL: 12, 13, 14, 15, 16, 17
SAP HANA: 2.00.076.00.1705400033

Each app must have its own database. Mendix apps cannot share data by sharing the same database.

If you want two apps to share the same database, then you need to share the data from one app to the other using APIs. In Mendix, these are supported by the Catalog or the REST and OData services described in the Integration section of the Studio Pro Guide. This is referred to as a microservices architecture.

For more information on why data cannot be shared between apps, see Data Storage. Use the Database Replication module if you need to copy the data from one app to another.

File Storage

Storage Services for Containers

For container-based deployments using Docker, Kubernetes, or Cloud Foundry, the following storage services are supported:

AWS S3
Azure Blob Storage
IBM Cloud Object Storage
SAP AWS S3 Object Storage
SAP Azure Blob Storage

For container-mounted storage in Kubernetes, provided by an external storage class, see also Use Docker with Minikube.

Storage Types for Servers

For server-based installations, the following storage types mounted by the OS are supported:

NAS
SAN
GFS
Local Storage

AWS S3 is also supported in the Windows Service Console.

Browsers

Google Chrome (latest stable desktop and Android versions)
Mozilla Firefox (latest stable desktop version)
Apple Safari (latest stable desktop version and latest version for each supported iOS version)
Microsoft Edge (latest stable desktop version)

Internet Explorer is not supported.

Mobile

For native and progressive web apps built with Mendix, the following operating system versions are supported:

Latest version of iOS
Latest three versions of Android

Only devices running on these operating system versions receive up-to-date security fixes from their vendors and thus minimize being vulnerable to known exploits.

You can build native and progressive web apps with Mendix that run on older operating system versions than the ones we support. However, to receive official Mendix support, you must demonstrate that your problem also occurs on a supported operating system version. The oldest operating system version where Mendix native mobile apps can run is determined by React Native.

Mendix recommends the following minimum hardware requirements for all mobile devices running native and progressive web Mendix apps:

CPU: minimum 2 cores with 2 GHz
Memory: minimum 2 GB

Depending on your app’s complexity, these minimum hardware requirements might not be sufficient and should be adjusted.

Developing native mobile apps with Mendix comes with special requirements explained in Native App Prerequisites and Troubleshooting.

MxBuild

MxBuild is a Windows and Linux command-line tool that can be used to build a Mendix Deployment Package. For more information, see MxBuild.

.NET 8
JDK 21

mx Command-Line Tool

The mx command-line tool is a Windows and Linux command-line tool that can be used to do useful things with your Mendix app. For more information, see mx Command-Line Tool.

Mono v5.20.x or .NET v4.7.2