Solutions
Corrdex fits how architecture work is already done.
Different teams use Corrdex differently, but the job stays the same: expose architectural risk, explain it clearly, and give engineers a direct path to the right file, rule, or violation.
What Corrdex changes
Code review shifts from subjective comments to explainable checks.
Files, violations, and rules become one connected system instead of isolated pages.
Teams spend less time rediscovering architecture decisions and more time acting on them.
01 / Free and Pro
For developers
Understand an unfamiliar codebase without spending days reading files in the wrong order.
Outcomes
Trace file relationships before making changes.
Ask targeted questions against real architecture context.
See blast radius before touching shared services.
Typical workflow
01Open a project and inspect the highest-risk files.
02Ask Corrdex how a service is wired and what depends on it.
03Move from file to violation to rule without losing context.
Where Corrdex helps
Working surface
FilesInspect the asset
ViolationsUnderstand what broke
RulesSee expected boundaries
Ask CorrdexQuery the architecture directly
02 / Team
For team leads
Keep PR review focused on architecture risk instead of re-checking the same boundaries manually.
Outcomes
Catch service-to-repository shortcuts before merge.
Track the files and rules driving architecture decline.
Turn review comments into enforceable rules.
Typical workflow
01Review the PR assessment and predicted violations.
02Drill into the file or rule causing the failure.
03Block risky changes only when Corrdex has clear evidence.
Where Corrdex helps
Working surface
FilesInspect the asset
ViolationsUnderstand what broke
RulesSee expected boundaries
Ask CorrdexQuery the architecture directly
03 / Enterprise
For engineering organizations
Standardize architecture expectations across teams without turning the platform group into a bottleneck.
Outcomes
Roll out rule packs across projects.
See which rules are failing most often across the org.
Give leadership a clear view of drift and compliance.
Typical workflow
01Publish shared policies once.
02Let project teams see violations in their own workflow.
03Use cross-project reporting to spot weak boundaries early.
Where Corrdex helps
Working surface
FilesInspect the asset
ViolationsUnderstand what broke
RulesSee expected boundaries
Ask CorrdexQuery the architecture directly
Deployment
Private deployment when SaaS is not an option
Enterprise teams with strict security or residency requirements can run Corrdex inside their own environment without changing the operating model.
Run in your own AWS, GCP, or Azure environment.
Keep indexing, rules, and AI context inside your network boundary.
Support regulated environments where SaaS is not acceptable.