Mendix Cloud is the default deployment option for Mendix applications: a public cloud service whose infrastructure is built and maintained by Mendix on top of Amazon Web Services, available in several regions.[1] Licensing an app on Mendix Cloud has two parts. The first is the user subscription, covered in the user subscriptions article. The second, covered here, is the plan and the cloud resources that run the app. Mendix documentation states that licences are sold as part of plans, and that a plan consists of a subscription to the plan, a cloud resource pack that specifies the resources available to an app environment, and additional resources such as fallback environments.[1]
Editions
Mendix Cloud documentation lists four plans: Free, Standard, Premium and Premium Plus.[1] The public pricing page shows Free, Standard and Premium. It lists Mendix Cloud as available in Free and at additional cost in Standard and Premium, and Mendix Cloud Dedicated, a single-tenant instance of Mendix Cloud, as available only in Premium at additional cost.[4] The pricing FAQ states that for Standard and Premium the compute resources are not included in the licence price, because Mendix supports several cloud deployment options.[4]
Free App
A Free App is a single, unlicensed environment on Mendix Cloud. Mendix documentation lists its main limits: unlimited users for a regular Free App, sleep mode after about an hour of inactivity, 0.5 GiB of database and 1 GiB of file storage, 0.5 vCPU, scheduled events that are not run, no custom domains, no support, and daily backups kept for up to two weeks.[1] A Free App that has been asleep for three months or longer may be archived, which deletes the running app, database, files and backups while the project and repository stay available.[1]
Licensed node
An app runs in production on Mendix Cloud only if it is linked to a licensed node.[7] A licensed app runs on a node with at least two environments, production and acceptance, and a test environment or Flexible Environments can be added.[1] Each environment runs one version of the app, and a different resource pack can be specified for each, although Mendix recommends that production and acceptance are the same size.[1] The node’s Technical Contact, who must have two-factor authentication enabled, links an app to a node. Linking a new app to a node unlinks the app already there, and linking a new project removes existing team members and resets node permissions.[7]
Metrics
Cloud Resource Packs
The Order Form Definitions define a Cloud Resource Pack as a standardized configuration of Mendix Cloud resources upon which an App Environment can be deployed.[3] The documentation lists current packs by size. The Standard, Premium and Premium Plus variants differ in availability features and in the sizes offered:
| Pack size | App RAM and vCPU | Database RAM and vCPU | DB and file storage | Standard tokens | Premium tokens | Premium Plus tokens |
|---|---|---|---|---|---|---|
| XS21 | 1 GiB, 0.25 | 1 GiB, 2 | 5 GiB, 10 GiB | 10 | not offered | not offered |
| S21 | 2 GiB, 0.5 | 2 GiB, 2 | 10 GiB, 20 GiB | 20 | 30 | not offered |
| M21 | 4 GiB, 1 | 4 GiB, 2 | 20 GiB, 40 GiB | 40 | 60 | not offered |
| L21 | 8 GiB, 2 | 8 GiB, 2 | 40 GiB, 80 GiB | 80 | 120 | not offered |
| XL21 | 16 GiB, 4 | 16 GiB, 4 | 80 GiB, 160 GiB | 160 | 240 | 400 |
| XXL21 | 32 GiB, 8 | 32 GiB, 4 | 160 GiB, 320 GiB | 320 | 480 | 800 |
| XXXL21 | 64 GiB, 16 | 64 GiB, 8 | 320 GiB, 640 GiB | 640 | 960 | 1,600 |
| XXXXL21 | 128 GiB, 32 | 128 GiB, 16 | 640 GiB, 1,280 GiB | 1,280 | 1,920 | 3,200 |
| XXXXL21-5XLDB | 128 GiB, 32 | 256 GiB, 32 | 1,280 GiB, 1,280 GiB | 2,240 | 3,360 | 5,600 |
The sizes are from the Mendix Cloud documentation and the token rates from the Cloud Tokens page.[1][2] Premium plans provide multi-AZ fallback and Premium Plus plans provide multi-region fallback.[1] With a Premium plan an app can be scaled horizontally, and to benefit from high availability an app needs at least two instances.[1] Mendix states that Mendix Cloud does not guarantee latency between app and database.[1] The Order Form Definitions also list resource packs for the Advanced Audit Trail service and the Cloud Event Broker, and fixed-capacity file and database storage units.[3]
Legacy packs
Legacy packs (XS20 to XXL20, the Strato, Meso, Iono and Magneto containers and the older S to XXL sizes) are still in use but cannot be bought by new customers.[1][3] The Cloud Tokens page states that legacy packs already purchased are converted into Cloud Tokens, at fixed published rates, when they are deprovisioned. Examples are XS20 at 10 tokens, XXL20 at 320, Strato at 12 and Magneto at 147.[2] The page also warns that a legacy pack combined with fallback may cause inaccuracies in the self-service consumption tool.[2]
Cloud Tokens
The Order Form Definitions define a Token as a pre-paid unit that an authorized user can temporarily convert into a licence to use pre-defined functionality, and Cloud Tokens as tokens used on the Mendix platform to consume cloud resources such as Cloud Resource Packs.[3] When tokens are applied they are not available until the user ceases to use the resource accessed.[3] Control Center documentation adds that tokens are bought in advance, can be redeemed for packs, and can be reused or kept if a resource is no longer needed. It states that Mendix Cloud Tokens expire on the end date of their associated contract.[2] All current packs are converted to token equivalents and aggregated, so a customer can provision resources of any type and size as specified in its contracts.[2] The Entitlements section of Control Center shows entitled, consumed and remaining tokens.[2]
GenAI Units
Mendix Cloud GenAI Resource Packs are described as a premium product that requires an additional purchase.[5] Model resource packs convert a monthly Cloud Token amount at 100 GenAI Units per Cloud Token, and units are consumed at a model-specific exchange rate, so one resource can serve several supported model families. There are no fixed capacity tiers, the amount can be adjusted, and unused units at the end of a bundle month do not carry over.[5] Knowledge Base Resource Packs provide a vector database for retrieval-augmented generation, and the Standard knowledge base pack costs 48 Cloud Tokens.[2][5] Mendix states that its AI services use third-party technologies and that customers must comply with the terms of those providers to maintain access.[5]
Maia Units
Maia Units give capacity for Maia Make in Studio Pro. They are provisioned in Control Center at 100 Maia Units per Cloud Token per month, reset every month and do not roll over.[6] Maia Units are required only for Maia Make; other Maia features, for example Maia Plan, do not need them.[6] Every Mendix account includes a base monthly allocation before any tokens are needed. Provisioning requires enough free tokens, a subscription based on the FY21 price list or newer, a single account and a single active enterprise platform subscription.[6] Upgrades take effect immediately, while downgrades and deprovisioning take effect at the end of the month.[6]
Counting / floors
The counting unit is the environment. Each production, acceptance, test or flexible environment on a licensed node is sized by one pack, and its token cost is fixed by the pack. The Order Form Definitions describe the Standard package as covering vertical scalability from XS to XL pack sizes, and Premium and Premium Plus as covering S to XXL.[3] The documentation pack table, however, shows Standard variants up to XXXXL21-5XLDB, so the package description and the current table should be read together against the Order Form.[1] No minimum token purchase is published in the documents reviewed.
Virtualization & partitioning
The documentation explains that a pack can use a fraction of a vCPU because several environments run, completely isolated from each other, on a single virtual machine.[1] The pack, not the underlying virtual machine, is the licensed quantity.
Cloud / BYOL
Apps on Mendix Cloud run on Mendix-operated infrastructure, so no customer cloud licence is brought. Mendix Cloud Dedicated is defined in the Order Form Definitions as Mendix Cloud running in the customer’s AWS VPC, operated by Mendix, with the cloud resources furnished separately by the customer through its own AWS contract.[3] Mendix on Azure draws on the same tokens: after a 120-day free period per new app environment, Mendix charges a fixed number of Cloud Tokens per app environment (14 as of 2025), irrespective of the number of clusters.[9] That model is covered in the deployment licensing article.
Programs
The Cloud Tokens programme and the Free App are the wrappers described above. Contract expiry matters to both. When a contract expires, the account and its apps are downgraded to Unlicensed mode: apps shut down after 2 to 4 hours, are limited to 6 concurrent users, and the Mendix Cloud application data is downloadable for 60 days and then permanently deleted.[8] Because tokens expire with the contract, renewal timing affects both resources and balances.[2] Mendix sends renewal emails starting 90 days before expiry.[8]
Out of scope
This article does not cover licence terms for deployments outside Mendix Cloud, user counting, support levels or version lifecycle. It does not state prices for packs or tokens, because the documents reviewed give token counts rather than currency amounts. Third-party model pricing is outside the Mendix documents reviewed here, except for the GenAI Unit conversion rate.