GitDiagram vs Structurizr: generated diagram or C4 model as code

Written by GitDiagram. Facts about Structurizr checked against its own docs on November 9, 2026 (sources).

Structurizr is a "models as code" tool for the C4 model: you describe your software (people, systems, containers, components) once in the Structurizr DSL and get many consistent diagrams from it, from system context down to deployment. It does not read your code, apart from a Java component finder you configure. GitDiagram reads a GitHub repository and draws its architecture automatically. Choose Structurizr for a deliberate, reviewed architecture model of one or many systems that you maintain over time; choose GitDiagram for a picture of an existing repository right now, or as a starting point for that model. Structurizr's hosted cloud service has reached end of life, so it now runs on your own machine or server.

Which to choose

Choose Structurizr when	Choose GitDiagram when
You follow the C4 model and want context, container, component and deployment views.	You want a diagram of a repository without writing a model.
You want several diagrams kept consistent from one model.	You are exploring code you didn't write.
The architecture spans many repositories or systems.	You want each box linked to its code on GitHub.
You want the model reviewed in pull requests like code.	You want something hosted and free.

The same repository

Structurizr has no automatic output to compare: a person writes the model. GitDiagram's diagram is a useful place to start one. Its Express diagram names 16 components; turned into Structurizr DSL by hand, the core of it might begin like this (our sketch, not Structurizr output):

workspace.dsl, written by hand

workspace {
    model {
        client = person "HTTP client"
        service = softwareSystem "Web service" {
            webapp = container "Express app" "" "Node.js" {
                app = component "Express Application" "lib/application.js"
                request = component "Request API" "lib/request.js"
                response = component "Response API" "lib/response.js"
            }
        }
        client -> app "Sends requests"
        app -> request "Augments request"
        app -> response "Augments response"
    }
    views {
        component webapp {
            include *
            autolayout lr
        }
    }
}

What Structurizr does

Structurizr was built by Simon Brown, who created the C4 model. From one workspace it renders system landscape, system context, container, component and code views, plus dynamic and deployment views, and it exports to PlantUML, C4-PlantUML, Mermaid, WebSequenceDiagrams, PNG, SVG or a static site. Its Java component finder can build a component view from Java code, using rules you write.

The hosted cloud service has reached end of life with no replacement. Structurizr now ships as one tool (a Docker image or a .war file) with local (formerly Lite) to view a workspace on your machine, server (formerly on-premises) for a team, a browser Playground and an MCP server. Everything is free except the prebuilt server, which is licensed per installation by number of users, from £300 a month for up to 20.

What GitDiagram does

Replace hub with diagram in a GitHub URL. An AI model reads the file tree, README and up to 12 source files and draws the main components in groups, each linked to its code; you can export the result as Mermaid.

GitDiagram's limits: it is a map of the important parts, not a complete dependency graph. It can simplify or leave things out, it works only with GitHub repositories, and it shows the repository as it was when the diagram was made (Regenerate makes a fresh one).

At a glance

Question	GitDiagram	Structurizr
What you get	One interactive architecture diagram: up to 34 main components in groups, with labeled connections and a written overview. Each component links to its file or folder on GitHub.	Every C4 view of a model you write, kept consistent, exported to many formats.
Reads the code	Yes. An AI model reads the file tree, the README and up to 12 source files; every linked path is checked against the real repository.	No, except a Java component finder driven by your own rules.
Setup	None. Replace `hub` with `diagram` in a GitHub URL, or paste the URL on the home page.	Write a DSL workspace; view it with the Docker image, the `.war` file or the Playground.
Hosting and privacy	Yes, with a fine-grained GitHub token that stays in your browser and is never saved on GitDiagram's servers.	Self-hosted only, since the cloud service ended.
Price	Free. Making new diagrams is free within a shared daily limit; after that you can add your own OpenAI API key.	Free, except the prebuilt server: from £300 a month for up to 20 users.

Questions

Is the Structurizr cloud service still available?

No. Structurizr's docs say the cloud service has reached end of life with no replacement. Use structurizr local or a self-hosted structurizr server instead.

Can Structurizr generate a diagram from my code?

Only component views of Java code, with the component finder and rules you configure. Otherwise you write the model. GitDiagram generates a diagram from any GitHub repository.

Sources

Checked on November 9, 2026. Products change: if something here is out of date, open an issue.