138% more reported CVEs per day in 2026 than last year.New: always-on Fixboxes. Vulnerable dependencies, fixed and verified.

Security testing

Penetration testing cost

A penetration test of a typical web application costs between $5,000 and $30,000 in published 2026 pricing guides, and a large network or multi-role platform can cost far more. The price follows the number of tester days, and the number of days follows the scope. Most ways to pay less come down to wasting fewer of those days.

Updated

Penetration testing prices by type

Typical ranges in published pricing guides from 2025 and 2026, in US dollars, per engagement:

Test Typical range What moves it
Web application $5,000 to $30,000 Number of user roles, pages and integrations, payments, single sign-on
API or SaaS application $4,000 to $20,000 and up Number of endpoints, roles and tenants
External network $5,000 to $20,000 Number of public IP addresses and exposed services
Internal network $7,000 to $35,000 Number of sites, hosts and network segments; on-site work

Mobile, cloud, IoT and red team engagements are scoped case by case and often cost more. Treat every figure here as a planning range, not a quote.

Penetration testing cost per hour and per day

Firms that bill by time quote a day rate, and published guides put it roughly between $1,000 and $3,000 per tester day, or about $200 to $300 an hour, with senior specialists above that. A fixed-price quote is a day rate multiplied by an estimate, so always ask how many tester days a quote contains. Two quotes for "a web application pentest" can differ by a factor of three simply because one firm plans three days and the other ten.

What drives the price

  • Scope: the number of applications, endpoints, roles and hosts.
  • Depth: authenticated testing with several roles takes longer than an anonymous test.
  • Box type: a black-box test spends paid days on reconnaissance that a grey-box test skips.
  • Seniority and location of the testers.
  • Compliance reporting: PCI DSS or customer-facing attestation letters add work.
  • Retest: included in some quotes, billed separately in others.

Pricing models: project, PTaaS and AI pentests

Model How you pay Fits
Fixed-scope project One price per engagement A yearly test or a test before a launch
Time and materials Day or hourly rate Open-ended or changing scope
Penetration testing as a service (PTaaS) A subscription or credits, with a platform for findings and retests Several tests a year, and teams that want findings in their tracker
AI pentesting Per run, per target or a subscription Testing after every release, between human tests

AI penetration testing costs far less per run than a human engagement, which is why it is changing how often teams test. It does not yet replace the human test that customers and auditors ask for, so for most teams it is an addition to the budget line, not a replacement for it.

How to get more from a pentest budget

  1. Fix the known issues first. Run your scanners and patch what they find before the test. Paying a tester to report an outdated library a scanner could have flagged wastes tester days. See vulnerability assessment vs penetration testing.
  2. Choose grey box. Give the tester credentials, architecture notes and API documentation, so the days go on attacking, not mapping.
  3. Hand over an SBOM. A list of every component and version in the release tells the tester where known weaknesses may sit, without days of fingerprinting.
  4. Scope by risk. Test the payment flow and the admin panel deeply, and the marketing site lightly or not at all.
  5. Ask what is manual. A quote that is mostly automated scanning should be priced like scanning.
  6. Agree the retest up front. And book it, because a report without a retest proves little.

What the price does not cover

The pentest describes your system on the days of the test. The builds that follow pull in new package versions, and new vulnerabilities are published in components that passed. Paying for a second pentest to catch those is the most expensive way to do it.

CRACI does not run penetration tests. It records every package each of your GitHub Actions builds pulls in, including the hidden dependencies that no lockfile lists, and checks those SBOMs again as new vulnerabilities are published, so you know which releases are affected between tests. The same SBOM is the one to hand your tester. See what a pentest misses.

Penetration testing cost: frequently asked questions

How much does a penetration test cost?

Published 2026 pricing guides put a typical web application pentest between $5,000 and $30,000. Network, cloud and multi-role platforms are scoped case by case and can cost much more.

What does a pentest cost per hour?

Published guides put day rates roughly between $1,000 and $3,000 per tester, or about $200 to $300 an hour, with senior specialists above that.

Why do pentest quotes differ so much?

Mostly because of the number of tester days they contain, and how much of the work is manual. Ask each firm for the days, the box type and whether the retest is included.

Is PTaaS cheaper than a traditional pentest?

Per test it is often similar. PTaaS pays off when you test several times a year and want findings, retests and reports in one platform.

Are AI pentests cheaper?

Per run, much cheaper, which makes testing after every release affordable. Most customers and auditors still expect a human-led test at least once a year.

How can we lower the cost of a pentest?

Fix what scanners find beforehand, give the tester credentials, documentation and an SBOM, scope by risk, and agree the retest in the quote.

Know what you ship between pentests

Record every package your builds pull in and see which releases each new vulnerability affects.

Book a demo