Great applications start with clarity on intent. And that clarity matters most at the very beginning.
The earlier teams align around goals, scope, and requirements; the cheaper and easier change is. But as development progresses, misalignment becomes expensive, leading to rework, delays, and friction between business and IT. In fact, teams spend a significant portion of their time, often up to 25% of delivery effort, on requirements clarification, refinement sessions, and rework caused by ambiguity.
Yet most projects don’t begin with clarity. They begin with scattered notes, stakeholder conversations, slide decks, and half-defined ideas. To help teams navigate this messy start of a project, we’re excited to introduce Maia Plan.
Maia Plan is the AI-powered planning engine within the Mendix Portal that transforms ideas, project briefs, and intake conversations into structured, high-quality, execution-ready delivery plans. Acting as your AI planning assistant, Maia Plan helps teams move from idea to sprint-ready execution, faster and with greater confidence.
Maia Plan turns unstructured inputs, workshop notes, idea dumps, intake discussions, or even a simple prompt, into a structured, build-ready backlog in one seamless flow.
It first creates a clear project scope with:
This establishes alignment early, ensuring everyone understands what is being built and why. Maia Plan structures the input and generates a first draft project scope, while your team reviews, adjusts, and approves the outcome, keeping human judgment at the center of every decision.
From there, Maia Plan generates a structured solution proposal, including:
Once reviewed and approved, these artifacts are created directly within Mendix Epics and connected to Maia Make in Studio Pro. The result: a validation-ready backlog, without manual story writing or time-consuming refinement sessions. From there, stories can be picked up by Maia Make in Studio Pro to generate the first pass of the application. Pages and logic are scaffolded based on the approved plan, giving teams a working starting point in minutes. That first version can immediately be shared with stakeholders for feedback and validation.
Maia Plan reduces manual backlog grooming and removes ambiguity at the start of the lifecycle.
Teams can:
What once took days now takes hours. But this isn’t a return to waterfall. Maia Plan doesn’t lock teams into heavy upfront documentation or rigid specifications. Instead, it brings the best of both worlds: the clarity and structure traditionally associated with detailed planning, combined with the speed, flexibility, and continuous validation of agile development. You get structured intent early, while still iterating fast.
By introducing structure at the very beginning, Maia Plan improves decision quality when change is still inexpensive and builds confidence before a single microflow or page is created. And because it connects directly to Maia Make, structured intent flows seamlessly into AI-assisted development in Studio Pro. No handovers. No translation gaps. Less rework. Faster delivery. Happier developers.
Together, Maia Plan and Maia Make create a continuous AI-powered flow, from idea to plan, from plan to working application.
We’re excited to announce Maia Make, the new AI experience inside Studio Pro that brings all of Mendix’s generative capabilities into a single, seamless chat interface. Whether you’re creating something entirely new or iterating on existing work, Maia Make streamlines your development workflow with a task-focused approach that keeps you in flow.
Until now, working with Maia meant using different tools focused on what you wanted to build. With Maia Make, everything happens in one place. Start a conversation, describe what you need, and let Maia do the rest. Whether that’s scaffolding a new domain model, generating pages, crafting OQL queries, or explaining complex logic.
The following existing capabilities are now part of a single chat interface:
Next to the existing capabilities, Maia is also significantly more powerful than before with the addition of an MCP client, user story linking, microflow generation, and being able to take a plan and execute it.
When a plan has been made inside Maia Plan, you can click on a button to immediately send this plan over to Studio Pro, select the user stories that you want Maia to take care of, and have Maia implement them for you. This makes it easier for developers to quickly implement and validate the plans that Maia created before.
Aside from taking a user story that has been made via a plan, you can also leverage the user stories manually inside Studio Pro, making sure you can have Maia take care of stories at different stages of your development process.
With the new MCP Client it is possible to connect Maia to any MCP server that you have access to. Connect seamlessly to Playwright, Figma, or any other MCP Server to leverage the information in there to enable Maia to make better decisions when generating or providing answers since it will be grounded in custom information.
We now support fully configured ‘CRUD’ microflows – ask Maia for what you need and watch it build the microflows for you.
An Event Sub-process is a specific type of sub-process as defined in the BPMN specification. Sub-processes in general are all about a compound of activities representing a grouped sequence of tasks (sub-flows) within a larger process. In the case of an Event Sub-process triggered by an Event. It is the way to support sub-flows that can be optionally executed alongside the main workflow or used as an alternative path to terminate your workflow.
As an example: imagine a customer service interaction process is ongoing (e.g., handling an inquiry, processing a return, updating customer information). During this interaction, the customer expresses an urgent complaint that needs to be escalated and resolved through a specific procedure. You want to ensure that this part of the process is being dealt with in a consistent manner and visually represented as part of your workflow definition.
How is this different from a Boundary Event you might ask? An Event Sub-process can be ‘triggered’ at any moment during the lifecycle of the workflow. It’s not tied to a specific Workflow task like the Boundary Event. The Event Sub-process on the other hand allows for a consistent, overarching mechanism to handle exceptions for the entire duration of the workflow. Read more about Event Sub-processes in our docs.
A responsive IDE is essential for productive Mendix development, yet large projects can sometimes slow Studio Pro down. Background processes such as error checking continuously analyze the project to keep developers informed, but in big applications this can consume significant memory and reduce responsiveness.
In this release, we have redesigned the error checking process to use far less memory. In some projects this reduces memory usage by up to a factor of two, making the IDE noticeably more responsive during everyday modeling. We are also experimenting with further speed improvements and are already seeing promising results. More enhancements will follow as we continue to make Studio Pro faster and smoother to work with.
Developers often work with multiple Studio Pro versions, which is why we offer the Version Selector. This small application ensures that any project opened locally or from the Mendix Cloud launches in the correct Studio Pro version. Until now, Mac users did not have access to this tool, leading to extra friction and slower workflows.
With this release, the Version Selector is now available on Mac as part of the Studio Pro 11.8 Mac Beta. Installing Studio Pro 11.8 automatically adds it, allowing you to open cloud projects and local project exports directly in the right Studio Pro version. Besides making it easier to open new projects, the Version Selector is also key to starting development with Maia in the cloud and then continuing with Studio Pro on Mac.
Developing native mobile apps requires quick feedback on real devices. Until now, Make It Native could only offer one App Store version and one TestFlight version, which meant developers could test only the latest Mendix release and the newest LTS or MTS version. This limited flexibility, especially for teams planning annual updates of their native mobile app.
With this release, Make It Native now supports the two most recent LTS or MTS versions instead of just one. We achieved this by publishing the second latest version as a previous build in TestFlight. Today this means developers can use Make It Native for versions 11.8, 11.6, and 10.24. You can access older versions by opening Make It Native in TestFlight and selecting Previous Builds. Please refer to our documentation for more details.
Efficient data synchronization is essential for creating smooth offline‑first experiences. When networks are slow, or large data sets are involved, sync operations can take longer than users expect. Giving users control over this process helps keep your apps responsive and reduces unnecessary waiting.
This release introduces a new nanoflow action that lets you cancel an ongoing synchronization. When called, the action immediately stops the active sync, allowing users to continue working and try again later. You can add this action to any nanoflow or button to create a more flexible and user-friendly experience.
This month we’re bringing the Gallery widget up to speed with Data Grid 2 by adding the same capabilities that we have recently introduced for Data Grid 2: custom pagination control, dynamic page sizing, and auto-select first item. Just like with the grid, you can now design your own pagination interface, bind pagination properties to variables for programmatic control, and automatically highlight the first item when data loads. With these additions, the Gallery widget offers the same level of flexibility and control as the Data Grid 2, giving you consistent options regardless of which presentation format best suits your needs.
On Mendix Cloud, you can add a custom domain for all your applications. To configure a custom domain, you must provide an SSL certificate, so that your application can prove the custom domain can be trusted. After uploading the certificate, you can use it to configure a custom domain for your environment. This becomes rather cumbersome if you have a lot of applications. You would have to upload the SSL certificate separately for every application. If you use a wildcard certificate, you must upload the exact same certificate to multiple applications. With the shortened lifespan of certificates in the future, replacing the SSL certificates for a landscape of applications becomes a strenuous job.
That’s why we’re happy to introduce Central Certificate Management! With this new feature, you can manage the certificates for all your applications on Mendix Cloud in a single location. You can upload a certificate once and then use it for all the custom domains for all your applications on Mendix Cloud. Central Certificate Management has a simple replacement flow, where you can replace one SSL certificate that is about to expire with a new SSL certificate that has a later expiration date. When a certificate is replaced, all custom domains that use the replaced certificate will be updated with the new certificate automatically.
This will save you a lot of time and manual effort, especially if you use a wildcard certificate. Instead of uploading the same certificate to all your apps and replacing it manually on all your custom domains, you only must upload the certificate once, after which you can replace it on all custom domains with one click of a button.
With Central Certificate Management you will also get a landscape-wide overview of all your SSL certificates. You can see which ones are used, what apps and environments use it, and what SSL certificates are about to expire. This will help you keep track of your SSL certificates.
This is only the first iteration of our Certificate Management. We will be adding APIs soon, so that you can automate your certificate management.
Exciting news for Mendix developers! We’re thrilled to announce a powerful enhancement in Mendix Cloud: Version Pinning. This innovative feature is designed to bring unprecedented consistency and predictability to your application deployments, ensuring a smoother, more reliable journey from development to production.
When you deploy a new application or promote an existing one, Mendix Cloud intelligently manages the platform configuration. For promotions between environments on Mendix Cloud (Kubernetes), version pinning automatically reuses the exact platform configuration that was active in your source environment. This ensures that the combination of runtime images, buildpacks, and supporting components you’ve thoroughly tested is precisely what runs in your target environment.
Whether you’re clicking Promote in the Mendix Cloud Portal or leveraging the pinEnvironment parameter in the Mendix Cloud API, you’re unlocking a new level of deployment confidence.
Version pinning is a testament to our commitment to providing you with the tools to build and deploy robust, high-performing applications with ease. Get ready to experience more predictable behavior, fewer headaches, and a truly consistent application lifecycle within Mendix Cloud!
We’re excited to announce the release of the Google Gemini Connector, a new integration designed to enable text generation capabilities within your applications.
Built on top of the OpenAI – Chat Completions API, the connector allows developers to leverage Google Gemini models while reusing the familiar operations and structure of the OpenAI-compatible API layer. This approach ensures a consistent development experience, reduces integration effort, and accelerates time to value.
For a deeper dive into configuration, capabilities, and supported use cases, check out the official documentation.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。