Pricing
One audit. One price. $200.
Flat per-audit pricing — the full pipeline runs every time, with a working exploit on every critical. Re-runs on a new commit are the same flat price, never a quote or a scoping call, and your team gets free audits to evaluate first. No subscriptions, no seats, no surprises.
One flat price. The whole pipeline.
per audit — one repo, one commit
- Full report
- Every finding with severity, exact file:line, and the vulnerable code.
- Working exploit for criticals
- Each critical is reproduced on a mainnet fork — proof, not just a write-up.
- Architecture artifacts
- Extracted invariants, assumptions, and design decisions your code relies on.
- Earned verdicts
- A finding is dropped only when the validator can cite the line that defeats it — otherwise it stays in front of you, flagged for review.
- Re-audit on every commit
- Same flat price, diffed against your last scan. No new scoping call.
- Versioned, shareable report
- A report link pinned to the commit, plus PDF export.
Risk classes covered
Reentrancy · oracle and price manipulation · access control and privilege escalation · accounting and invariant drift · unchecked external calls and return values.
Ready to start?
Connect a GitHub repository, select the target branch and commit, and start the audit.
One-time payment per audit · Charged in USD at checkout · No card on file
If your audit doesn't complete, you don't pay — a re-run or a full credit.
No trap. No meter. No surprises.
You commit weekly — so the real question is what the bill looks like on a repo you keep pushing to. Here's exactly how it works.
One charge
What counts as one audit
You're billed once when you start an audit on a commit, and codebase size doesn't change the price — one repo, one commit, one $200 charge.
Re-runs
Re-audits are the same flat price
−3 critical, −5 high vs previous scan
Push a fix, run again. Each re-audit is its own $200 audit, diffed against the last — no new scoping call, no subscription. Continuous security, billed per run.
Reliability
A failed run isn't a charge for nothing
If an audit fails to complete, you shouldn't pay for nothing. Message us in the chat and we'll make it right — a re-run or a credit, not a charge for a report you never got.
Evaluate first
Teams get free audits to start
A team workspace ships with a configurable allowance of free audits, so the whole team can evaluate Guardix on real repositories before paying. One chat message provisions it.
The rest of what a security buyer asks.
Code privacy
Cloned to audit, not to train
- Not training data
- Your code is cloned to run the audit and is never used to train models.
- Data handling
- What we can read, what we keep afterwards, which model providers see your code, and how to get it deleted — spelled out on the security page. Organization-specific questions: message us in the chat.
Chains supported
EVM Solidity, exploit on a fork
Solidity source analysis on any EVM chain. Exploit proofs for critical findings run on a mainnet fork.
Products & stage
What you can buy today
- Code audit$200 per audit
- Live
- PR reviewRequest access
- Early access
- Release audit$200 per audit
- Beta
Frequently asked questions.
Still weighing it against a manual engagement? Run Guardix first and on every fix, then spend the human budget on novel attack paths. Read the full comparison →
Run your first audit.
Connect a GitHub repository, pick a commit, and get a full validated report in hours — $200, flat. Teams get a free-audit allowance to evaluate.