Why not just use Mendix™ Maia?
A fair question, and the honest answer is that Maia and mxto sit at different points in the lifecycle. They compose rather than compete.
Maia is Mendix's native AI assistance inside the Mendix™ Platform: it helps a developer working in Studio Pro build faster, with in-context suggestions. mxto is the AI delivery engine that works on the model from outside the IDE. It lets an AI agent read, author, and ship an application headless, at estate scale, in CI, with a round-trip fidelity check on every change. If Maia is the assistant beside the developer in the IDE, mxto is the toolchain an autonomous agent drives across the whole estate.
| Mendix™ Maia | mxto | |
|---|---|---|
| Runs | Inside the Mendix™ Platform / Studio Pro | External and headless (no Studio Pro in the loop) |
| Primary user | A developer building in the IDE | An AI agent you bring (Claude Code, Cursor, your own) |
| Focus | In-context assistance while you build | Whole-model read, author, build, deploy, test |
| Working set | The developer's current work | Estate scale (hundreds of modules, thousands of flows) |
| Fits into | The Mendix™ authoring experience | CI pipelines and agent workflows |
| Fidelity | Native authoring | Round-trip-verified (0 unexpected diffs) |
Want the evidence behind the mxto side of that table? The proof pack has the reproducible read, the round-trip fidelity certifications, and the honest boundaries.