Features

Corrdex is built for architecture review, not dashboard decoration.

Every feature is meant to answer a specific engineering question quickly: what is drifting, what is risky, what rule was violated, and what should be inspected next.

Core jobs
Detect structural problems before they become team-wide habits.
Explain findings with enough evidence that engineers trust them.
Connect files, violations, rules, and impact so users can navigate naturally.
Index
Architecture drift detectionBoundary enforcementChange impact analysisArchitecture memoryGovernance rulesCodebase radar
01

Architecture drift detection

Corrdex maps the codebase continuously and flags when files start crossing boundaries they were not supposed to cross.

What it gives you
Expose service, controller, and repository shortcuts early.
Show the specific dependency path that caused the drift.
Keep architecture review tied to real files instead of abstract diagrams.
Drift signal
Fileapi/users.ts
Unexpected accessdb/postgres.ts
Expected routeAPI -> Service -> DB
StatusNeeds review
02

Boundary enforcement

Rules do not stay as documentation. Corrdex can fail a review when a change violates a boundary your team has decided to enforce.

What it gives you
Block direct imports across forbidden layers.
Turn recurring review comments into durable policies.
Keep standards consistent across contributors and teams.
Rule outcome
RuleUI cannot access Payments directly
PR stateBlocked
Offendercomponents/checkout-form.tsx
Expected pathUI -> Payments API
03

Change impact analysis

Before a risky merge lands, Corrdex shows what the likely blast radius looks like and which assets should be inspected next.

What it gives you
Rank high-fan-out files before they break downstream paths.
Show which flows and files are likely affected by a change.
Help reviewers focus on the right surfaces first.
Impact snapshot
Modified fileauth/token.ts
Downstream routes42
Impacted components18
RiskElevated
04

Architecture memory

Corrdex keeps an explainable record of how the system is structured so new contributors are not relying on stale wiki pages.

What it gives you
Tie explanations back to current code evidence.
Expose role, behavior, and dependency assumptions directly in the product.
Reduce onboarding time for unfamiliar services and domains.
Memory entry
DomainCore
RuleCore must not import Infrastructure
Verified2 minutes ago
SourceCurrent code structure
05

Governance rules

Model architecture expectations as rules with enough structure to enforce, explain, and refine them over time.

What it gives you
Create shared rule libraries across projects.
Inspect the file and violation connected to every rule.
Move from policy intent to actual enforcement without leaving the platform.
Rule shape
type: BOUNDARY
name: Controllers cannot access repositories
from: ROLE(controller)
operator: CANNOT_ACCESS
to: ROLE(repository)
06

Codebase radar

Find the hotspots worth attention first instead of manually searching for coupling, drift, and risk patterns across the whole repository.

What it gives you
Surface the files driving architecture degradation.
Highlight central modules and rising coupling points.
Give teams an operating view of where refactor effort should start.
Hotspot ranking
PaymentService.tsHealth impact -3
SettlementService.tsHealth impact -2
PaymentController.ts2 active violations
TrendWorsening
Ready to keep your architecture honest?

Stop letting architecture drift.
Start enforcing it.

Your first repo is free. No install, no config, no excuses.

Analyze your repo free →Book a demo