Static analysis · Debt forensics
Code Archaeologist scans your monolith, maps every dependency, and prices the damage — in dollars, not story points. Then it hands you the extraction order.
Solution · The dig method
Rewrites fail because nobody knows what's buried. Code Archaeologist surveys first, prices everything, then extracts one module at a time.
One command against any Java or C# codebase. Runs entirely on your machine — read-only, nothing leaves your network.
local · :8088 · offlineA sub-minute sweep maps every dependency, flags cycles, god classes, and injection risks — and attaches a dollar estimate to each finding.
1,247 files · 47sA strangler-fig extraction queue ranks modules by effort and risk, so the next safe move is always at the top of the list.
5 candidates rankedFeatures · Field equipment
Every finding carries a cost estimate and a confidence range — so prioritization conversations happen in the language your CFO speaks.
Force, circle, and tree views of your module graph. Cycles glow. Hover a node and see exactly what it drags down with it.
A ranked extraction order — effort-graded, risk-graded — telling you which module to carve out first and which to leave buried.
Findings sorted CRIT / HIGH / MED / LOW with rule and rationale attached. Open them, or push straight to your issue tracker.
Every run is recorded. Watch the debt number fall scan over scan — and prove the refactor budget paid off.
Runs on your machine, serves on localhost, works air-gapped. Your source never leaves the building.
Pricing · Pick your kit
Run a full scan on one repo, no card required. Pay when you're ready to keep digging.
For individual developers, OSS projects, and one-off scans of a legacy codebase.
For engineering teams using Code Arch as part of their regular modernization work.
For larger organizations, regulated industries, and teams with compliance requirements.
Air-gapped or on-prem deployment? Get in touch — that's our favorite kind of site. · Compare all plans & read the FAQ →
About · Why "archaeologist"
Every monolith is a record of decisions that made sense at the time. The teams that fail treat it like a demolition job — and lose the load-bearing walls along with the rubble. The teams that succeed dig carefully.
We built Code Archaeologist after watching too many rewrites collapse for the same reason: nobody could see what was buried, or what it would cost to move. So we made the tool we wanted on day one of every migration — one that surveys before it touches anything.
The scanner observes. It never rewrites your code or phones home.
Estimates with ranges and methodology you can audit — currently v0.4, published openly.
Incremental extraction beats big-bang rewrites. The queue exists so you never have to guess the next move.