A web application firewall sits in front of your app or API and filters out malicious HTTP traffic — SQL injection attempts, cross-site scripting, credential-stuffing bots, and the long tail of OWASP Top 10 attacks — before it reaches your servers. It’s infrastructure-layer security, which is why the three tools worth comparing here come from very different corners of the industry: Cloudflare is a CDN/edge network that bundles WAF into its plans, AWS WAF is a pay-as-you-go primitive built for anyone already running on AWS, and Imperva is a dedicated application-security vendor selling WAF as its core product. We pulled every number below directly from cloudflare.com and aws.amazon.com/waf/pricing, and confirmed Imperva’s pricing is not publicly listed.
At a Glance
| Platform | Pricing model | Entry price | WAF on entry tier? | Best known for |
|---|---|---|---|---|
| Cloudflare WAF | Flat-rate plan tiers | $0/mo (Free plan) | Yes — included even on Free | Simplicity, bundled CDN + WAF + DDoS |
| AWS WAF | Pure pay-as-you-go (per web ACL, rule, and request) | No subscription — usage-based, from ~$5/mo for one web ACL | Yes, but priced à la carte | Deep AWS-native integration (CloudFront, ALB, API Gateway) |
| Imperva Cloud WAF | Not public — quote-based | Contact sales | Yes, on all plans (scope depends on quote) | Low false-positive managed rules, dedicated threat research team |
Short Verdict
Cloudflare is the fastest path to “some WAF protection” for almost nothing — it’s literally on the free plan — and scales cleanly into paid tiers as you need compliance features and SLAs. AWS WAF is the right call if your app already lives behind CloudFront, an Application Load Balancer, or API Gateway, because it’s billed by the component (web ACL, rule, request) rather than by plan, which can be cheaper or pricier depending on traffic shape. Imperva is the choice for security teams who want a vendor-managed rule set tuned by a dedicated research team and are willing to go through a sales process to get a number — it’s priced like an enterprise security product because, unlike the other two, that’s Imperva’s whole business.
What Each Platform Actually Is
Cloudflare WAF ships as a feature bundled into Cloudflare’s CDN plans rather than sold separately. Per cloudflare.com/plans, the Free plan ($0/month) already includes the WAF, a free managed ruleset, unmetered DDoS protection, and a universal SSL certificate. Pro ($20/month billed annually, or $25 billed monthly) and Business ($200/month annually, or $250 monthly) add more managed rules and features; Business is the first tier with PCI DSS 4.0 compliance and an uptime SLA. The top tier — which Cloudflare’s own pricing page now labels “Contract” rather than “Enterprise” — is custom-priced and adds things like network prioritization and higher-multiplier uptime service credits.
AWS WAF has no plan tiers at all in the traditional sense — it’s billed per component. Per aws.amazon.com/waf/pricing: $5.00 per web ACL per month, $1.00 per rule (or per managed rule group) per web ACL per month, and $0.60 per million web requests at the default inspection level, with small surcharges if you raise the Web ACL Capacity Unit (WCU) limit or inspect larger request bodies. Allow, Block, and Count actions carry no extra charge. Add-on modules are priced separately: Bot Control costs $10/month per web ACL plus $1 per million requests (first 10 million monthly requests free), and the Fraud Control modules (Account Takeover Prevention, Account Creation Fraud Prevention) are $10/month per web ACL each plus tiered per-request fees. New AWS customers get a limited allocation under the AWS Free Tier for the first 12 months.
Imperva Cloud WAF is a SaaS WAF managed through the Imperva Management Console, positioned around “near-zero false positives” because its managed rules are written and tested by Imperva’s own Threat Research team before release, rather than relying purely on automated rule generation. Imperva’s product page lists integrated bot protection and API security, machine-learning “Attack Analytics” that correlates alerts into incident narratives, automated SSL certificate management, file-upload scanning, a Terraform provider, and an AI Assistant for natural-language investigation. Imperva also sells on-premises (WAF Gateway) and Kubernetes-native (Elastic WAF) deployment options alongside the cloud product. None of this comes with a published price — every path on the page leads to “Schedule demo,” “Contact Us,” or a free trial sign-up.
Pricing Breakdown
| Platform | Published rate | Notes |
|---|---|---|
| Cloudflare Free | $0/mo | WAF, managed ruleset, unmetered DDoS, SSL, SSO, RBAC all included |
| Cloudflare Pro | $20/mo (annual) or $25/mo (monthly) | Adds performance features (image optimization, AMP) |
| Cloudflare Business | $200/mo (annual) or $250/mo (monthly) | Adds PCI DSS 4.0 compliance, 100% uptime SLA, 1x service credits |
| Cloudflare “Contract” tier | Custom, billed annually | Adds network prioritization, 10x–25x uptime service credits |
| AWS WAF base | $5/web ACL/mo + $1/rule/mo + $0.60/million requests | Billed hourly-prorated; scales with number of ACLs and rules |
| AWS WAF Bot Control | $10/mo + $1/million requests (10M free) | Separate add-on per web ACL |
| AWS WAF Fraud Control | $10/mo per module + tiered per-request fees | Account Takeover Prevention and Account Creation Fraud Prevention are priced separately |
| Imperva Cloud WAF | Not published | Quote-based; free trial available at imperva.com/free-trial |
Pros and Cons
Cloudflare WAF
- Pros: Genuinely free tier with real WAF protection; predictable flat pricing; bundled with CDN, DDoS protection, and SSL; easiest onboarding of the three.
- Cons: Advanced compliance and SLA features gated behind Business and Contract tiers; custom rule depth is lighter than a dedicated application-security vendor.
AWS WAF
- Pros: True pay-as-you-go with no plan lock-in; tight integration with CloudFront, ALB, API Gateway, and AppSync; granular control over rules and WCU budget.
- Cons: Costs stack up fast once you add Bot Control and Fraud Control modules; pricing structure (WCUs, body-inspection tiers, CAPTCHA fees) takes real effort to model correctly; no bundled CDN or DDoS product unless you’re also paying for CloudFront/Shield.
Imperva Cloud WAF
- Pros: Managed rules vetted by a dedicated threat research team; strong analytics and incident correlation; flexible deployment (cloud, on-prem, Kubernetes) under one vendor.
- Cons: No public pricing anywhere — every evaluation starts with a sales call; likely overkill (and over-budget) for a small team that just needs baseline protection.
Who It’s a Good Fit For
Choose Cloudflare if you want WAF protection today with zero procurement process, or you’re already using Cloudflare for DNS/CDN and want it bundled in. Choose AWS WAF if your application is already running on AWS infrastructure and you want security billed the same granular way as the rest of your stack — and you’re comfortable modeling costs component by component. Choose Imperva if you’re a mid-size-to-enterprise security team that wants a vendor-managed, actively curated rule set and dedicated support, and your budget process can absorb a quote-based enterprise security purchase.
Who Should Look Elsewhere
If you need multi-cloud WAF coverage (not just AWS) with a single pane of glass, neither Cloudflare’s app-specific rules nor AWS WAF’s AWS-only scope will fully satisfy you without extra tooling — that’s a case where Imperva’s cloud-agnostic positioning, or a dedicated multi-cloud security platform, is worth the sales conversation.
Bottom Line
These three aren’t interchangeable line items — Cloudflare sells WAF as part of a broader edge-network subscription, AWS sells it as a metered infrastructure primitive, and Imperva sells it as a dedicated, support-heavy security product. For most small-to-mid-size teams, Cloudflare’s free-to-$200/month ladder is the easiest decision to justify. Teams already deep in AWS should model AWS WAF’s per-component costs against their real traffic before assuming it’s cheaper. And any team that needs white-glove rule tuning and incident analytics should expect to get Imperva on the phone rather than finding a number online.
FAQ
Is the WAF on Cloudflare’s Free plan actually usable, or just a teaser?
Per Cloudflare’s own plan comparison, the Free plan includes the WAF along with a free managed ruleset, so it’s a real (if more basic) deployment, not a disabled demo.
How much does AWS WAF cost for a typical small site?
At minimum, one web ACL with a few rules runs roughly $5–$10/month in base fees, plus $0.60 per million requests — the real cost driver is add-ons like Bot Control ($10/month + per-request fees) if you need them.
Why doesn’t Imperva publish any pricing?
Imperva sells WAF as an enterprise security product with variable scope (traffic volume, number of sites, deployment model), which it — like most enterprise security vendors — prices through a sales conversation rather than a public rate card.
Can I use AWS WAF if my app isn’t hosted on AWS?
AWS WAF is designed to attach to AWS resources (CloudFront, Application Load Balancer, API Gateway, AppSync, Amplify, Cognito, Verified Access), so it’s not a general-purpose option for non-AWS-hosted applications — Cloudflare or Imperva fit that case better.
Does any of these offer a free trial?
Cloudflare’s Free plan is a permanent free tier, not a trial. AWS WAF has no trial as such — you simply pay for usage, with a limited free allocation under the AWS Free Tier for new accounts. Imperva offers a dedicated free trial sign-up at imperva.com/free-trial.
