EOModeller EOModeller
Sign in Get started
About

A modelling tool, by someone who models for a living.

EOModeller is built and maintained by 1AV Ltd — a New Zealand company founded by an architect who couldn't find a modelling tool he was willing to keep using, and decided to build one. Everything on this page is plain language about who EOModeller is for, what 1AV believes about modelling, and how we run.

Who EOModeller is for

The architect who opens Excalidraw fifteen minutes into the meeting, not the enterprise platform their organisation pays for. The consultant who needs to hand off the architecture as a real artefact, not screenshots. The team lead who wants a place to think about systems that isn't a whiteboard photo or a 600-cell spreadsheet.

EOModeller is sized for the individual and the small team — two to ten people, working closely together. We are deliberately not building an enterprise platform. The product won't grow approval workflows, SSO scaffolding, or a permissioned reference-architecture repository. If those are what you need, several incumbents serve that market and serve it well.

What we believe about modelling

Most architectural work isn't documentation.
It's thinking, aligning, deciding, communicating, learning, reasoning about change. Each is a distinct purpose; each rewards a different style of artefact. A tool that optimises only for documentation is hostile to most of the work. (Why create models?)
Every artefact lives somewhere in a formality–detail quadrant.
The sketch, the whiteboard explosion, the overview, the reference specification — different positions, all real. Architects move between them within a single piece of work. A modelling tool should treat formality and detail as first-class properties, not styling tricks. (The shape of an architectural artefact)
Notation pluralism beats notation monoculture.
Real architecture diagrams mix ArchiMate, UML, cloud icons, and ad-hoc shapes on the same canvas. A tool that forces a single notation forces architects to translate. The metamodel underneath should support multiple notations cleanly. (Notation conformance)
Standards are a feature, not a constraint.
EOModeller implements UML 2.5.1 and ArchiMate 3.1 to the specification — not approximations of them. When we defer something, we say so on the conformance page. No "supports UML" with asterisks hidden behind marketing copy.
Code generation is your job, not ours.
EOModeller exports UML 2.5.1 XMI at a stable URL. Your script, LLM, or templating engine turns it into code. We don't ship a language mapping — your transform is closer to your toolchain than ours could ever be. (XMI export guide)
The web is the deployment target.
Not a desktop install, not a Java applet. Modern browsers are capable enough to host the editor; web deployment is what makes collaborative work tractable; and a model that lives on a URL is one that can be referenced by every tool the architect already uses.

How we run

Pricing for individuals, not enterprises.
One Pro tier at $19 USD/month, or $15 USD/month billed annually ($180 USD/year). No per-seat multipliers, no negotiated contracts, no procurement cycle. The Free tier is meant to be useful, not a 30-day trial in disguise.
Hosted in Australia, ours to operate.
Production runs in Microsoft Azure's Australia East region. Operational details are in our privacy policy. Data residency is a real concern for some customers; if it's one for you, the answer is currently "Australia, not elsewhere."
Documented gaps.
Every modelling tool has gaps. The notation conformance page lists ours per diagram type. If a gap matters to you, tell us — your input shapes what we ship next, in ways that procurement-driven roadmaps can't reach.
Communications shaped like a person, not a company.
You'll hear from us when there's something to say. No newsletter, no nurture sequence, no marketing emails by default. Support is support@eomodeller.com; a person reads each one.

What's not here yet

EOModeller is in early release. We're honest about what's in and what isn't:

  • Real-time co-editing across a team — works for two to three; production stress testing is in progress.
  • BPMN as a dedicated notation — UML Activity covers the architect's 80%; a BPMN profile pack is post-launch.
  • C4 as a dedicated notation — UML Component diagrams with stereotypes are the C4-alike at launch.
  • GCP cloud profile — AWS and Azure ship at launch; GCP is post-launch.
  • Inline comments, public read-only links, restore-from-snapshot — all post-launch per the published planning records.

The notation conformance page is the canonical list. If you want detail beyond that, ask.

Get in touch