Corrdex — Keep Your Architecture Honest
GitHubSign inDemoGet Started →<br>Team reviews code.<br>Corrdex reviews architecture.<br>Turn architectural decisions into enforceable rules. Corrdex helps teams detect drift, review structural changes, and keep systems healthy as codebases and organizations scale.<br>Start for free ->Book a demoView pricing<br>•No agent installs•Works with any TS/JS repo•CI/CD native•Free tier available<br>Focused Benchmarks<br>Built for fast indexing and controlled AI token burn, not vague architecture theater.
Repo scale<br>8k files<br>Large TypeScript and JavaScript codebases
Ingestion speed<br>Fresh indexing without waiting on long CI loops
AI answers<br>9.5k avg<br>Current answer baseline after prompt compaction
Token efficiency<br>4k-14k<br>Tight function, file, and trace ranges
corrdex/acme-backend<br>Scanning
0files analyzed<br>0drift detected<br>0broken boundaries
Architecture map
CheckoutControllerPaymentServiceOrderRepositoryInvoiceWorker
Live findings<br>DRIFT<br>Wrong-layer import<br>CheckoutController imports OrderRepository directly.
VIOLATION<br>Boundary broken<br>InvoiceWorker writes to the HTTP response layer.
IMPACT<br>Blast radius: 38 files<br>A change in PaymentService now fans out across checkout.
Last scan: 2s ago · TypeScript2 merges blocked
The real cost of architectural debt<br>Your codebase grows.<br>Your architecture does not keep up.<br>Every team starts with good intentions. Over time, the wrong imports creep in, responsibilities blur, and the original structure becomes invisible. Reviews do not catch it. Documentation does not survive. And the engineer who understood it all just got promoted.<br>Corrdex exists so that does not happen to you.
"Why is our service layer calling the DB directly?"<br>Architecture drift accumulates invisibly across hundreds of PRs. Nobody sees the pattern until it's too late.
"I'm terrified to touch this module."<br>No visibility into change impact. You do not know what breaks until it already has.
"The only doc we have is the original engineer's memory."<br>Architectural knowledge evaporates with every team change. There is no institutional memory.
"We want to enforce architecture but can't scale reviews."<br>Manual architecture review does not scale past 3 engineers. Rules in docs do not run in CI.
10 features, one platform<br>Every layer of architectural governance — built in.
01<br>Architecture Drift Detection<br>Stop architecture rot before it requires a full rewrite.<br>Flags every file accumulating the wrong responsibilities continuously, automatically, and early in review.<br>continuousautomated
Controller<br>Repository
02<br>Boundary Enforcement<br>Stop architectural violations before they reach production.<br>Controllers can't call repos. Services can't reach the HTTP layer. Rules enforced at every import, in real time.<br>real-timeCI/CD
Controller<br>Repository
03<br>Change Impact Analysis<br>Know every file a change can affect before the PR is merged.<br>Blast radius mapped and risk-scored at PR-time. Your reviewer sees structural risk before they even open the diff.<br>PR-timerisk-scored
PaymentSvc
38 files affected
04<br>Architecture Memory<br>Your architecture survives team turnover.<br>Every decision, every rule, and every boundary stays visible across reorgs, departures, and new hires. Your architecture does not depend on one person's memory.<br>persistentorg-wide
Team<br>Alexdeparted<br>Samdeparted<br>Danadeparted
Architecture Rules<br>rule('no-ctrl-repo', {<br>from: 'controller',<br>forbidden: ['repository'],<br>})
✓ Rules persisted — 3 engineers later
05<br>Team Architecture Governance<br>Your best engineers' judgment, enforced at scale.<br>Encode what your senior engineers know. Run it in CI. Block violations automatically where code changes happen.<br>TypeScript rulesCI-blocking
rule('no-controller-repo',<br>severity: 'error'<br>blocking: true
✓ 3 violations blocked in CI today
06<br>PR Architecture Review<br>Merge blocked. Architecture violation caught at commit time.<br>Every PR gets a full structural health check. Violations surface before review. Merges can be blocked automatically without manual policing.<br>merge-gatingGitHub · GitLab
PR #847 · feat/order-servicemerge blocked<br>✓CI / Build<br>7 jobs passed
✓Tests<br>47 / 47 passed
✗Architecture<br>2 violations<br>↳ checkoutController → OrderRepository<br>↳ orderService → HTTP layer
08<br>System Topology Visualization<br>See your architecture the way it actually is.<br>An interactive live graph of every layer, dependency, and coupling score updated as your codebase evolves.<br>interactivelive
APIPaySvcOrderSvcPayRepoOrdRepoStripe
10<br>Codebase Radar<br>Understand any codebase in seconds. No README required.<br>Point it at any repo and get a complete architectural map of layers, owners, and boundaries quickly. Useful for audits, due diligence, and day-one onboarding.<br>instantany repono setup
Scanning...<br>controllers/checkout.tscontroller<br>services/payment.tsservice<br>repos/order.tsrepository<br>workers/invoice.tsqueue-worker<br>config/stripe.tsconfig<br>✓ 247 files classified
checkoutauthpaymentorderRepopayRepoDB
07<br>Architecture Diff<br>See what actually...