CodeLensREBUILD ESTIMATORBack to overview ↗FREE TOOL · NO ACCOUNT REQUIRED
What would it take
to build it again?
Turn your source into a transparent rebuild-cost scenario. Adjust the assumptions. Take the range into your next planning conversation.
Select the source
A folder, not a commitment.
No ZIP extraction or repository access needed. Select text source; dependencies, generated output and common secret filenames are excluded.
800 files maximum · 1 MB per readable file · 20 MB total. Files are read only on selection. No source upload, server retention, analytics submission, training use, or browser storage. Results keep aggregate counts only. Reload or “Clear” discards them. Secrets embedded inside source may be read locally—filename filtering is not a secret scanner.
Set your assumptions
These defaults are an illustrative USD scenario, not a surveyed market rate. Productive lines/hour describes rebuild effort, not typing speed. Rates update the scenario without reading your files again.
A range, not a guess
disguised as a valuation.
Select your code or try the example to see scope, language mix, testing signals and an explainable cost range.
OPEN THE BLACK BOX
You should be able
to challenge the number.
How this range is calculated
- Hourly rates are editable example assumptions, not verified market prices.
- Production effort = meaningful source lines / selected productive lines per hour, multiplied by 1 + branching adjustment (capped at 80%).
- Reproducing existing tests adds test lines / 70 hours (low) or / 25 hours (high). Test presence is not coverage or quality.
- Minimum base effort: 4–8 hours. Planning, review and integration allowance: 15% low / 65% high.
- Comment and branch counting is heuristic; strings and language syntax can affect the counts.
- No estimate of IP/market value, security, design quality, business requirements, infrastructure, licenses, data migration, external services or maintenance.
- Missing tests/docs are uncertainty signals, not proof that those activities have no cost. Treat the range as a scenario to discuss with an engineer.
Branching adjustment: heuristic keyword/operators count ÷ production lines × 4, capped at 80%. Comments/strings can affect counts. We do not claim cyclomatic complexity or test coverage.
A DIFFERENT QUESTION?
Understand what needs fixing.
A rebuild estimate is free. Evidence-backed website and repository audits are separate paid services; checkout and execution remain unavailable pending activation.