Guide · Mendix licensing
How much does Mendix cost? A guide for CTOs and CFOs
There is no single answer to the question of Mendix pricing. The licensing cost is the outcome of a few independent decisions you make before you ever talk numbers. This guide does not quote price ranges: it explains what the cost consists of and which questions to answer before talking to a Mendix partner.
What makes the Mendix licensing model different
Mendix does not license application complexity. It does not matter how many screens, integrations, business rules or workflows you have. That sets it apart from many traditional systems where adding functionality automatically raises the license cost. Instead, the cost is based on four variables.
One specific application or a portfolio of initiatives?
Who are they, how many, and how do they use the apps?
Where and how do you want to run the applications?
Which platform plan and add-ons do you need?
1. How many applications?
For organizations that want to build one specific application: a customer portal, a ticketing system, a process management app. Cheaper to start with, but uneconomical if there are more plans.
An unlimited number of applications under one agreement. It becomes economical at two or three applications already. The option for organizations that treat Mendix as a strategic platform, not a one-off project.
- One specific project or a portfolio of initiatives?
- Are more applications planned within 12-24 months of the first one?
- Could different departments use the same platform?
2. Users: who and how many?
This is one of the most complex parts of the model. Mendix distinguishes several user categories and treats each differently.
Employees who log in to the apps: sales reps in a CRM, HR staff, managers approving requests. Each is counted individually; the cost grows with the number of people.
Customers, partners, suppliers. Logged-in external users are counted, usually at a different rate than employees. Anonymous users (e.g. a public portal) are usually not licensed individually, though session or traffic limits may apply.
People building applications in Mendix Studio Pro do not count towards user licensing. They have a separate model, usually included in the platform plan.
- How many people in the organization will use the apps (estimate)?
- Will the app be available to customers or external partners?
- Will external users log in or use it anonymously?
- Will the user count stay stable or grow dynamically?
3. Where and how will you deploy?
Deployment models differ in the level of control, responsibility for infrastructure and cost. Every application needs at least two environments: test and production. In practice you usually need three: Development/Test, Acceptance (UAT) and Production.
Managed Mendix infrastructure on AWS. Hosting, updates, security and monitoring are on Mendix. The simplest option: zero infrastructure on your side.
Your own isolated cluster in the Mendix cloud, with no resource sharing. For organizations that require stronger data isolation and predictable performance.
Mendix on your own infrastructure: Azure, AWS, Google Cloud. Full control over data and compliance, but it requires your own DevOps team.
Deployment on your own servers. Maximum control and maximum responsibility. Mendix charges for platform support in this model.
For organizations in the SAP ecosystem: Mendix runs directly on SAP Business Technology Platform.
- Must the data stay in the EU or in a specific country?
- Do security policies require your own infrastructure?
- Do you have a team able to run a private cloud or servers?
- Do you use SAP, and does BTP integration matter?
4. Environment sizing (XS to 4XL)
Regardless of the deployment model, every environment has a size that determines the available compute and memory. A small prototype runs on XS. An application serving hundreds of concurrent users with many integrations needs an M, L or larger environment. Environment size directly drives hosting cost. When budgeting, it helps to have at least initial assumptions about:
- the expected number of concurrent users,
- the intensity of operations (simple forms vs complex calculations and integrations),
- response time requirements.
5. Platform plan
Platform plans differ in available capabilities, SLA level and support.
A free plan for learning and prototyping. No availability guarantees, community support only. Not suitable for production use.
A plan for applications operating at department or organization level. Full application lifecycle, multiple environments, broader configuration.
A plan for business-critical systems: full platform access, advanced infrastructure control, 24/7 support, 99.95% availability, a dedicated Customer Success Manager, all deployment options.
The key question: how critical will the application be for the business? Is an hour of downtime a problem, or a disaster?
6. Add-ons
Beyond the base license, Mendix offers optional modules that extend the platform.
Detailed data change logs, useful for compliance and audit requirements.
Application quality and security analysis, especially relevant for larger development teams.
Built-in tools for automated application testing.
Some are free in the Mendix Marketplace; premium ones require a separate license.
How to approach an initial estimate
Before you sit down to talk pricing, prepare answers to the questions below. The more of them you have ready, the more accurate the quote you can get.
- How many apps do you plan within 1-2 years?
- Internal, external, or both?
- How critical is each of them?
- How many employees will use the apps (in total)?
- Will customers or partners have access?
- Will they log in or use it anonymously?
- Is the user count stable or growing?
- Where must the data live: regulations and policies?
- Do you have your own cloud (Azure, AWS, GCP) or servers?
- Do you use SAP?
- Who owns IT infrastructure?
- How many concurrent users at peak?
- Complex calculations or large data volumes?
- Audit or compliance requirements for operation logging?
- Do you need automated tests?
- What SLA (availability) level is expected?
That is normal. We work part of them out together during a short discovery, before any offer is made.
What goes into the cost of Mendix licensing
Single App or Unlimited Apps.
Billed per user.
Logged-in users billed per user, at a different rate than employees.
Public Cloud, Dedicated, Private Cloud, On-Premise or SAP BTP.
From XS to 4XL, billed per environment.
Standard or Premium, depending on how critical the app is.
Audit Trail, Quality & Security, Test Automation.
Omitted external users, too few environments, a plan too small for a critical app.
The cost of Mendix licensing is predictable and scalable, provided you know what you need.
Want to discuss a specific scenario?
45 minutes with a certified Mendix architect, no strings attached. As an authorized reseller we will help translate your needs into a licensing architecture. During the Proof of Value the license is free.
New to Mendix? What is Mendix →
Roadmap: your own Mendix team in 90 days →
Related services