A modelling tool made for practising architects.
Principled. Web-native. Quadrant-native. Built for the work architects actually do — not the enterprise platforms they're given.
Every architectural artefact lives somewhere in the formality–detail quadrant.
Philippe Kruchten observed that architectural representation evolves from informal metaphor to structured formalism, and from sparse sketch to complete specification. Every diagram an architect produces sits somewhere in that two-dimensional space. The trouble is that every existing modelling tool forces a single position.
The enterprise platforms chose formal-detailed as the only legitimate position. The casual diagramming tools made no commitment at all. Balsamiq chose informal-moderate-detail and defended it for fifteen years. Architects work across all four quadrants every week, and currently have to switch tools to move between them — losing their work to redrawing each time.
EOModeller treats formality and detail as first-class properties of every diagram. The same artefact can start as a sketch, grow into a draft, and become a reference — on the same substrate, without being re-authored. Pick the position; the tool's visual rendering and validation behaviour follow from it.
No other modelling tool works this way. Sparx has hand-drawn mode and a whiteboard style, but they are decorative — buried in menus, disconnected from the model's meaning. In EOModeller, the position is the model's stance toward itself.
The tool you'd choose — not the one you're given.
The modelling tool market has been captured by enterprise platforms bought over the heads of the people who actually use them. Architects inside those organisations routinely reach for something else.
"Fifteen minutes into the meeting, the architect opened Excalidraw. Three wobbly rectangles, arrows between them, ninety seconds. The organisation pays several hundred thousand dollars a year for an enterprise architecture platform. The architect did not open it."
This happens every day. It's not a training gap. It's a revealed preference. The imposed platform succeeds at inventory, compliance, and executive reporting — and fails at the architect's actual job: producing artefacts that communicate design with precision under time pressure.
EOModeller closes the gap between the imposed platform and the casual diagramming tool. It opens as fast as Excalidraw. It produces artefacts that survive the meeting. It respects that architects already know what they're doing — and gets out of the way.
It is a tool for individuals. It is priced for individuals. It is deliberately not an enterprise platform, and will not become one.
A modelling substrate, not a checklist of features.
Built from a principled metamodel rather than a union of notations. Every capability below follows from the same underlying structure.
Built on the notations you already know.
EOModeller doesn't replace established standards — it implements them faithfully and lets you work across them without friction. The notation conformance page lists exactly what's supported at v1.0, at what fidelity.
Models That Matter
Architectural modelling for the modern age.
A method alongside the tool.
EOModeller is the implementation of a method. Models That Matter is the explanation of the method — a working architect's account of what principled modelling looks like in 2026, and why most tools and most practice have drifted away from it.
The book and the tool reinforce each other. Neither stands alone. The framework published in the book is what EOModeller implements; the practice EOModeller enables is what the book describes.
- The work architects actually do
- The formality–detail quadrantAvailable now
- Three layers of element identity
- Artefact boundaries and delegation
- Notation pluralism and the principled metamodel
- Modelling in the age of AI agents
Join the pre-release programme.
For practising architects and small teams. No enterprise sales motion. No demos with salespeople. Just the tool, when it's ready.