Creator and maintainer
Lukas Niessen
Lukas started ArchUnitTS to solve a real architecture-testing gap and now stewards the shared direction across the library family.
View profile →Five people, one shared standard.
We are a team of five people building architecture tests that feel native in every ecosystem they serve.
We work across language tooling, graph analysis, developer experience, cloud platforms, and applied AI, with open-source collaboration at the center.
Team
The people building ArchUnit.
A small, multidisciplinary team focused on one practical outcome: keeping architectural intent close to the code.
Language & Ecosystem Lead
Tristan Kruse
Tristan contributes across ArchUnitPython and leads the development of ArchUnitRuby and ArchUnitJava. His work focuses on translating a shared architecture-testing model into language-native APIs, analyzers, test integrations, and developer workflows across different ecosystems.
View profile →
AI and platform engineering
Jan Heimann
Jan brings applied AI, MLOps, and platform experience to the question of how architecture guardrails support fast-moving engineering teams.
View profile →
Python engineering
Deban Kumar Sahu
Deban develops ArchUnitPython and brings hands-on experience with Python APIs, data tooling, and maintainable backend design.
View profile →
Cloud and developer experience
Robey Beswick
Robey connects cloud engineering with pragmatic developer workflows, helping the project keep delivery and usability in the same conversation.
View profile →Origin story
A missing TypeScript guardrail became a family.
ArchUnit started with a concrete problem. While working as a consultant, Lukas needed an architecture-testing framework for TypeScript with the practical depth of ArchUnit in the Java ecosystem. The available options did not fully fit the project, so he began building ArchUnitTS in his spare time.
Contributors joined, enterprise projects brought new requirements, and the original dependency rules grew into metrics, diagrams, reports, and test-runner integrations. The same idea then moved into Python, .NET, Ruby, Rust, Zig, Go, Java, and PHP.
Each implementation respects its own language. What connects them is the belief that an architecture decision becomes more useful when the test suite can prove it after every change.
Read the full project story →Every contribution counts
The wider contributor community.
Documentation, fixes, examples, features, and thoughtful feedback all move an open-source project forward.
Build with us
There is room for your perspective.
Explore an open role, contribute in an ecosystem you know, or talk with us about architecture guardrails for your team.