Mendix 11 launched on June 26, 2025, and over the following year it grew – one monthly release at a time – into the platform’s most significant leap in years, culminating in the 11.12 Long-Term Support (LTS) release on June 30, 2026. This is the overview: the big picture, a Mendix 9 vs 10 vs 11 comparison, and a guided set of deep dives into every part of the release. Skim it in a few minutes, then follow the links into whatever matters to your apps.
The big picture: what Mendix 11 is really about
Strip away the month-by-month detail and four shifts define Mendix 11:
- AI moved from “assist” to “generate.” Maia, Mendix’s GenAI layer, can now scaffold an entire app from a text description, image, or PDF – and generate workflows, pages, and OQL queries. The Agents Kit and MCP Server turn Mendix into a platform for building agentic apps, not just a tool that uses AI to check your work.
- The React client is the new default. New apps use the modern React-based Mendix client; the legacy Dojo client is deprecated and slated for removal in Mendix 12. This is the biggest architectural change – and the thing to plan your upgrade around.
- Enterprise operations grew up. Zero-downtime deployments, bundled OpenTelemetry tracing, offline-first data access at general availability, and a clear LTS/MTS lifecycle make Mendix 11 a more serious production platform.
- Workflows and integration matured. BPMN boundary events, far richer consumed-REST tooling, view entities with a real OQL interface, and Data Transformers round out the fabric around the app.
Mendix 9 vs 10 vs 11: how the platform has changed
If you are still on Mendix 9 or 10, here is how the three most recent major versions compare at a glance.
| Dimension | Mendix 9 | Mendix 10 | Mendix 11 |
|---|---|---|---|
| Support & lifecycle | Supported (oldest of the 3 current majors, until Mendix 12 GA ~2027); 9.24 is the final 9.x LTS | Supported; 10.24 LTS | Current; 11.6 MTS, 11.12 LTS |
| Web client & UI | Dojo client (Atlas 3) | Dojo default; React client available (opt-in) later in the 10.x line | React client is the default; Dojo deprecated (removed in Mendix 12); Atlas 4 available (optional upgrade) |
| AI | MxAssist Performance & Logic bots | Best Practice Bot, ML Kit GA; early Maia GenAI | Maia GenAI: generate apps, pages, workflows, OQL; Agents Kit; custom LLM providers |
| Java / runtime | Java 11 (17 added later) | Java 11/17, then Java 21 from 10.21 | Java 21 required |
| Workflows & BPMN | Workflow editor (beta) | Workflows GA; multi-user tasks & decision methods | Advanced BPMN: boundary events, recurrence; Maia-generated workflows |
| Data & integration | Task Queue; external entities; PWA | Business Events; View Entities & OQL v2 (10.19); AWS connectors | Offline-first data GA; Data Transformers GA; richer OQL & consumed-REST |
| Version control | SVN default; Git added in 9.12 (no new SVN apps from 9.24) | Git only; existing SVN apps must migrate first | Git-native; SVN fully retired |
| Headline theme | Unified low-code (workflows, PWA, AI-assist) | “A New Era” – enterprise-scale, cloud-native | “Start with AI, Build Anything” |
Upgrading from 9 or 10? The essentials: the React client is now the default and Dojo is deprecated, so custom or Marketplace Dojo widgets need migrating; Java 21 is mandatory (Mendix 10 already forced this at 10.21); and there are real runtime breaking changes – entity access is enforced on the home-page microflow, XPath math operators must be explicitly enabled, some deprecated Java APIs were removed, and apps still carrying pre-Mendix-5.12 file documents will not start. The practical path is 9.24 (LTS) then 10.24 (LTS) then 11.12 (LTS) – step through the LTS releases rather than jumping.
The deep dives: everything in Mendix 11, by theme
The complete feature set, split into six focused reads. Start anywhere:
- AI: Maia, Agents, and MCP – Maia Make and Maia Plan, the Agents Kit, Model Context Protocol in both directions, and a production-ready GenAI stack for the apps you ship.
- Studio Pro: the React-first IDE and developer experience – a React-first client, modernized editors and a better version-control UI, big performance gains, and a far richer extensibility surface.
- UI: the React client, Atlas 4, widgets, and mobile – the default React client and Atlas 4, the iframe-free Embedded Client, upgraded Data Grid 2 and Gallery, and PWA-first mobile with offline-first data at GA.
- Data and integration – OQL as a full query language, view entities, optimistic locking, richer REST and OData, the External Database Connector, Data Transformers, and Change Data Capture.
- Logic and workflows – a smoother microflow and nanoflow editor, return-value mapping, richer OQL and XPath, plus BPMN boundary and notification events with AI agents as workflow steps.
- Security and governance – Mendix Policies, central audit logs, SSO and license governance, application and runtime security hardening, and Software Composition for supply-chain visibility.
Deploying and running Mendix 11? How and where you host apps – Kubernetes and Azure, the portable runtime, zero-downtime releases, networking, and observability – is version-independent, so it lives in a separate four-part Mendix Cloud series.
Making sense of it all
Mendix 11 is a genuine platform shift: AI-native development on a modern React client, running on a hardened, observable enterprise runtime. The month-by-month releases can make it hard to see the forest for the trees – but taken together, 11.0 through 11.12 move Mendix from “low-code with AI assistance” to “AI-first application development.”
If you are planning an upgrade from Mendix 9 or 10, or want to know which of these features are worth adopting first for your specific apps, that is exactly the kind of thing our team helps with day to day.