Skip to content

Software architecture platform

Architecture you can read, run and refute.

Arch Hub treats architecture as an artefact rather than a slide deck. Models live in version control, diagrams are generated from them, and every design is held to the same standard as the code it describes: API-first, contracted, sustainable and testable — so a drawing can be checked instead of believed.

Read the principlesExplore the landscape

Why treating architecture as an artefact pays off

What teams say changes once the model is the source of truth — and the diagrams, the contracts and the tests all come from it.

  • “The diagrams used to be a slide someone redrew before a review. Now they are generated from the model in the repository, so the only way to change the picture is to change the thing it describes.”

    Architecture as code

  • “Writing the boundaries down as a context map settled arguments we had been having for a year. It turned out we disagreed about which team owned a concept, not about the technology.”

    Domain architecture

  • “Once the interface between two contexts was an explicit contract, the upstream team could refactor freely and we stopped finding out about changes from a failing integration.”

    Integration architecture

  • “A design you cannot test is a design you cannot refute. Making the seams explicit is what let us put a test around a boundary instead of around the whole system.”

    Quality engineering

  • “The honest measure of sustainable architecture is how cheap the next change is. Keeping the models in version control means we can see where the cost is accumulating instead of guessing.”

    Engineering leadership

Areas