What problem does ArchSteer solve?

AI agents write code faster than any architect can review, document, or govern. Docs rot instantly, the real architecture is invisible, decisions are made silently, and intended architecture drifts. ArchSteer makes architecture continuously observable and governable.

How is ArchSteer different from a linter or a diagram tool?

Linters check single-language rules; diagram tools require manual upkeep. ArchSteer maintains one code-derived model that powers living docs, auto-drafted ADRs, conformance with a net-new ratchet, an evolution feed, and AI-agent steering — all from the same source of truth.

Do I have to set up rules before I get value?

No. The read-only X-ray runs with zero config: point it at any repo and instantly see the current architecture and how it changed. Declaring intent for governance is an incremental, opt-in upgrade.

How does ArchSteer steer AI coding agents?

It injects sharp, file-scoped guardrails into CLAUDE.md / AGENTS.md / .cursor/rules that point at the governing ADR, so agents build toward the target architecture instead of copying adjacent legacy code.

Home › Migrations

Migrations

Migrating a monolith to a modular architecture

Decomposition fails when new code crosses the boundaries you're trying to create. ArchSteer encodes allowed dependencies and enforces them continuously.

Declare the module boundaries

Express allowed and forbidden dependencies between modules as fitness functions.

Steer agents to respect them

Guardrails keep agents from creating cross-module dependencies that violate the target.

Track the decomposition

Conformance and the evolution feed show boundaries hardening over time.

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.

▶ Live demo Talk to us

FAQ

Modular monolith or microservices?

Either — ArchSteer enforces dependency direction regardless of deployment topology.

How are violations handled?

Existing crossings are baselined; net-new ones are blocked in CI.

Migrating a monolith to a modular architecture

Declare the module boundaries

Steer agents to respect them

Track the decomposition

Try it on your repo

FAQ

Modular monolith or microservices?

How are violations handled?

Related

Migrating from Express to Next.js route handlers

Migrating raw SQL to the repository pattern

Migrating from JavaScript to TypeScript