home / how pricing works
// pricing
Priced by effort, not by package
We scope every engagement in person-days against your real attack surface. That keeps it honest: you pay for the hands-on testing your systems actually need — not a fixed tier that over- or under-serves you.
// what drives cost
What changes the number
A few factors decide how many person-days an engagement takes. We work them out with you on a short scoping call.
Attack surface size
Number of apps, endpoints, APIs, user roles and environments in scope.
Complexity
Custom auth, multi-tenancy, payment flows and intricate business logic take longer to test well.
Test type
A focused web pentest, a full mobile + backend test, a cloud review or an objective-led red team all scope differently.
Access model
Black-box takes longer than a credentialed test with documentation and test accounts.
Retest & cadence
A one-off test, or a recurring quarterly cadence and a running bug bounty program.
Reporting needs
Standard report, or extra artefacts for a specific audit or customer requirement.
// how scoping works
From enquiry to quote
- 01
Tell us the targets
Share what you want tested and roughly when. A short form or a 30-minute call is enough to start.
- 02
We scope it
We estimate person-days against your surface and send a clear proposal — scope, dates, deliverables and price.
- 03
You approve
Sign the scope letter and we schedule. No surprise add-ons once the scope is agreed.
// what's always included
In every quote
- Manual-first testing — no cost padded with scanner dumps
- A full report with CVSS-scored, reproducible findings
- One free retest of every finding after you fix
- A readout call to walk your team through the results
Get a number for your scope
Tell us what you're building and we'll come back with person-days and a price. No obligation, no hard sell.