Tool 08 · Planning · Free
Audit Scope & Quote Estimator
Lines of code, contract count, chain, complexity and urgency in — a price range, a timeline in working days and a researcher count out. Every coefficient is in one editable config object, so nothing here is a black box.
At a glance
Audit Cost Estimator
Run it
Exclude tests, interfaces you don't own, and vendored libraries such as OpenZeppelin.
How it works
What this tool does, and what it can't.
The model is deliberately simple and fully visible: a base fee covering scoping, reporting and verification, plus a per-line rate, multiplied by complexity, chain and urgency factors, with a contract-count adjustment. The quoted range is that midpoint spread by a fixed band, floored at our entry price.
Timeline is derived from the fee at a working day rate, then stretched by complexity and compressed by urgency — because rushing an audit does not reduce the work, it just costs more to fit it into fewer days.
What it cannot model is the thing that moves real quotes most: the state of your tests and documentation. Good coverage lets researchers spend their time hunting instead of reconstructing intent, and routinely shifts a quote by thirty percent in either direction.
Starting points: pre-deployment assessment from $1,500, standard audit from $3,000, DeFi protocol audit from $8,000, bridge audit from $15,000, invariant suite from $4,000, retainer from $3,000/month. Scope drives the final figure, and every engagement is quoted after a free review of the repository.
Because nobody has read your code yet. Test coverage, documentation quality, the number of external integrations and how novel the design is all move the number, and none of them are visible from lines of code alone. Real quotes follow a scoping review that takes under two working days and costs nothing.
Novel economic design, many external integrations, upgradeable architecture, thin documentation, low test coverage, non-EVM chains and urgency. What makes it cheaper: a well-documented fork of known code, high coverage, a tight scope and flexible timing.
One to four weeks for most engagements, plus two to five days for remediation verification after your fixes land. Bridges run four to eight weeks because there is a threat model per chain plus the off-chain relay layer.
Yes — every coefficient lives in one CONFIG object at the top of js/estimator.js. We publish it rather than hiding it because a pricing model you cannot inspect is a sales tactic, not a tool.
Beyond automation
No tool reads your specification. We do.
The findings that drain protocols come from state assumptions, economic design and cross-contract interaction — none of which a scanner sees. Free scoping in under two working days.