Introduction to Modeller
Understand the situation, choose the intervention, and model the change.
Modeller helps teams understand a business situation, agree what better means, compare possible interventions, and design the selected change. Technology is one possible intervention, not the assumed destination.
When an Initiative selects a technology intervention, the System Design workspace turns concise domain definitions into consistent source code while keeping the model, architecture, and generated output visible.
Start here
Have a change request in hand? Start a Discovery Session at modeller.website — it runs in the browser, needs no account, and gives you a link to share with your Domain Expert.
Start a Discovery Session
Open an Initiative at modeller.website and work through it with a Domain Expert.
Initiatives
Follow Discover, Frame, and Shape from a change request to selected interventions.
Try the playground
Explore System Design in the browser with a working example.
System Design
Install the tooling and generate your first project.
Core concepts
Understand initiatives, models, generation, templates, and ownership.
Reference
Look up the DSL, CLI, configuration, and data types.
The central idea
An Initiative records the original request, observed problem, desired outcomes, constraints, and selected interventions. If technology is selected, a recorded cross-reference connects that intervention to System Design. The handoff does not invent or scaffold model content automatically.
Within System Design, the domain model records what the business means. Template packs translate that intent into the conventions of a particular architecture. Generated and handwritten code remain clearly separated, so regeneration is safe and the result stays understandable.
AI assistance is optional. It can propose questions, interventions, explanations, and model changes, but people curate and accept them through the same explicit Modeller interfaces available without AI. The core does not require a particular provider.