ArchSteer vs ArchUnit
ArchUnit is excellent for JUnit-based architecture rules in the JVM. ArchSteer covers the broader job — observability, governance, decisions, and agent steering — across languages.
Scope
ArchUnit enforces rules you hand-write as Java tests. ArchSteer derives a model and adds living docs, ADR capture, and an evolution timeline on top of conformance.
The ratchet
ArchSteer blocks only net-new violations against a baseline, so existing debt doesn't force a freeze — ideal mid-migration.
AI agents
ArchSteer steers Cursor/Claude toward the target, which ArchUnit doesn't address.
Try it on your repo
Run `archsteer xray` on your repo to see this in under a minute, then declare intent when you're ready to govern.
FAQ
Can I use both?
Yes — keep ArchUnit's JVM rules and add ArchSteer for cross-language governance, docs, and agent steering.
Is ArchSteer JVM-only?
No — it's language-agnostic, with TS/JS and Python today.
Related
ArchSteer vs dependency-cruiser
dependency-cruiser lints JS/TS dependency rules. ArchSteer adds a code-derived model, migr…
ArchSteer vs Structurizr
Structurizr models C4 diagrams as code you maintain. ArchSteer derives the model from your…
ArchSteer vs CodeRabbit
CodeRabbit reviews PRs with AI. ArchSteer maintains the architecture's system of record — …