| How the model is authored | A canvas: drill into a system to see its containers, into a container to see its components. | Structurizr DSL — text you write, from which the views are generated. |
|---|
| Where it lives | A hosted workspace, or JSON files on your machine with the desktop app. | Files in your repository, rendered locally, on-premises or by the hosted service. |
|---|
| Review in a pull request | Branches and change sets inside the model, with a merge view; the desktop JSON also diffs in git. | Native — the DSL is a text file, so the diff is the review. |
|---|
| Documentation and contracts | Markdown, PlantUML sequences, ER tables, OpenAPI and Protobuf contracts attached to the element they describe. | Markdown and ADRs attached to the workspace, rendered alongside the diagrams. |
|---|
| AI coding agents | A hosted MCP server: agents read the model and write back to it with scoped tokens. | The DSL is text an agent can edit; the site describes it as AI friendly. |
|---|
| Audience outside engineering | A link opens the diagram; viewers need no tooling and no DSL. | Readers need the rendered views published somewhere for them. |
|---|
| Licence and price | Free in the browser with an account. Desktop is €10 a month after 7 days; the Community edition is open source. | Open source and free to run yourself; the hosted service is a separate product. |
|---|