Visible
Teams can inspect the graph, rule, and evidence.
Our mission
Make architecture a capability every team can exercise.
Software structure should not depend on someone remembering a diagram. It should remain visible, testable, and open to deliberate change.
Why this matters
Architecture is the accumulated effect of everyday decisions.
Most structural decline is not caused by one dramatic choice. It comes from thousands of reasonable local changes that no longer add up to the system teams intended to build.
We build ArchUnit so engineers can state the boundaries that matter, evaluate them with real source code, and receive feedback while the context for a change is still present.
Our aim is not to freeze design. It is to make change explicit. A useful architecture rule creates a shared point of discussion, a testable expectation, and a record of when a team chooses a different direction.
Native
The API belongs in the language and test culture around it.
Actionable
A failure explains the decision and the path back to a healthy state.
Adaptable
Rules support deliberate evolution rather than preserving yesterday forever.
The work ahead
A shared architecture language, expressed natively.
Explore the principles that guide our decisions and the people translating them across ecosystems.