# Cloudflare Pricing 2026: Plans and What You Pay
By Marielos Chévez · 2026-11-01 · Source: https://www.activepieces.com/blog/cloudflare-pricing-2026-plans-and-what-you-pay
---
[Cloudflare](https://www.cloudflare.com/plans/) sells **five tiers: Free, Pro, Business, Enterprise** and the Workers Paid developer plan.
Cloudflare prices zone plans per domain and Workers per account, and bills usage and add-ons on top, which is the kind of line item that surfaces only when you wire up automations in tools like [Activepieces](https://www.activepieces.com) and watch the request counts climb.
## Cloudflare pricing in 2026, plan by plan
Start from the plan name and you'll under-budget.
### Cloudflare plan prices compared in one table
The table below is the plan ladder as of 1 November 2026, and it shows what each tier is built to carry and where it stops.
Exact dollar amounts change, so take them from Cloudflare's plans page on the day you sign.
| Plan | Monthly, billed annually | Monthly, billed monthly | Key inclusions | Key limits |
|---|---|---|---|---|
| Free | No charge | No charge | DNS, basic DDoS protection, universal SSL | Thinnest rule allowances; most gated features absent |
| Pro | Per-domain fee on the plans page | Per-domain fee on the plans page | Web application firewall (WAF) managed rules, image optimization | Priced per domain; support stays self-serve |
| Business | Per-domain fee on the plans page | Per-domain fee on the plans page | Higher rule allowances, stronger support terms | Still per domain; advanced products sold separately |
| Enterprise | Custom quote | Custom quote | Negotiated features and support | Contract-bound, so cost is set by the sales conversation |
| Workers Paid | Account-level base fee | Account-level base fee | Larger compute and storage allowances | Use beyond the allowance is metered |
Plan-gated features and usage meters never appear in the headline fee.
Ten client sites means ten subscriptions, because every domain carries its own plan, whether you track renewals by hand or in a workflow tool. Add-ons and meters attach per product on top, so price each domain separately before you quote.
## Free plan coverage and limits
Start every domain on Free, which covers DNS, CDN, basic DDoS protection and universal SSL. It stops at small rule caps, so the question per domain is whether those caps are enough.
What runs out first is rules. The caps on Free, per [WP WAF Manager](https://www.wpwafmanager.com/docs/main/general/cloudflare-free-plan-limitations/), are 5 custom WAF rules, 3 Page Rules, 10 single redirects and 10 cache rules.
### Cloudflare plan limits that force an upgrade
Upgrade to Pro and those caps rise to 20 custom WAF rules, 20 Page Rules, 25 single redirects and 25 cache rules.
After a site migration, when old URLs can number in the hundreds, ten redirects is a problem. **The jump from 10 to 25 cache rules** matters to anyone tuning performance by path.
Because these caps apply to each domain, one busy client can't borrow another's allowance. Upgrading that client to Pro is a cost you should pass on, and not absorb into a shared account.
A small brochure site, a portfolio or a low-traffic blog can stay on Free indefinitely, provided it needs only a handful of rules and a short redirect list.
Once a domain carries a store, a login or a migration history, budget for Pro on it from the start and quote it that way.
## Pro, Business and Enterprise plan protections
Each step up the ladder buys a different kind of protection, so the plan you quote should follow the risk on the domain, not the size of the site.
| | Pro | Business | Enterprise |
|---|---|---|---|
| Price | Fixed monthly, per domain | Fixed monthly, per domain, well above Pro | Quoted per contract |
| WAF and managed rules | Included | Included, with more tuning | Included, with the most control |
| Custom rule count | 20, up from 5 on Free | Higher than Pro | Highest, set by contract |
| Support level | Standard ticket support | Priority support | Named account team |
| SLA/uptime guarantee | None offered | Financially backed | Financially backed, negotiable |
| Custom SSL | Not included | Included | Included |
| Image optimization | Included | Included | Included |
Put SLA, custom SSL and support in the quote, since those are the rows that move the bill.
### Pro: where the WAF and image tools start
Pro is the first plan with the managed WAF and image optimization, so it's the cheapest tier where a store or login page is defensible.
Business is where you pay for accountability. The uptime guarantee and priority support only matter if the client's contract promises something similar, so bill Business only to clients who've signed for that promise.
Until sales gives you a number, Enterprise has no budget line, because it has no sticker price. Treat it as a separate project with its own scope, and keep it off any shared account where other clients would quietly carry the cost.
## What Cloudflare costs at three realistic usage levels
Budget roughly $0 for a small site, **$600 a year for a growing one** and $1,260 for five domains, before storage, which is where the surprises sit.
Assume Pro at $20 a month per domain, Workers at a $5 monthly base, and Argo at $5 plus $0.10/GB on 200 GB a month. Each column shows what add-ons do to the plan price.
| | Small site | Growing SaaS/ecommerce | Multi-domain business |
|---|---|---|---|
| Plans | Free, $0 | Pro, $240 | Pro × 5, $1,200 |
| Add-ons (Argo $5 + $0.10/GB) | None | ($5 + $20) × 12 = $300 | None |
| Workers $5 base | None | $5 × 12 = $60 | $5 × 12 = $60 |
| Domain count | 1 | 1 | 5 |
| Annual total | $0 | 240 + 300 + 60 = $600 | 1,200 + 60 = $1,260 |
The growing column costs two and a half times its plan price, so the plan name is the smallest line you'll have to defend.
### A growing store or SaaS
$240 a year buys Pro, and Argo and Workers push the total to $600, so Argo and Workers together cost $360 annually. Storage can dwarf both.
One streaming app's [public breakdown](https://www.answeroverflow.com/m/1402150142726897766) shows Pro at $240, R2 reads at $159 and Workers at $132.48.
R2 storage alone was $1,438.2, bringing the year to $1,969.68. **Storage was roughly 73% of that bill**, so size the object store before you quote the plan.
Run five Pro zones and the plans cost $1,200, with one Workers subscription adding $60. Plans are per domain, so a shared account hides the cost.
The busiest domain's API and storage usage lands on the same invoice as four quiet ones. **Meter each domain and bill it to its owner, or the quiet ones subsidize the loud one.**
## Hidden costs and limits that surprise Cloudflare customers
The loud domain is loud because of charges the plan name never mentions. They're add-ons, usage meters, rule caps that depend on the plan tier, and a multiplier for every zone you add.
Move 2 TB a month through Argo smart routing and it adds roughly $200. Argo costs $5 a month plus $0.10 per GB after the first GB, so the charge can exceed the plan it sits on.
### Usage meters on developer products
When a client's app gets busy, it is billed by traffic, not by the tier you quoted. **Workers overages run $0.30 per million requests** and $0.02 per million CPU-milliseconds.
When a client's app gets busy, it is billed by traffic, not by the tier you quoted.
R2 also charges for operations, meaning each read and write, so a bucket of many small files costs more than the same bytes in a few large ones.
The egress comparison from [ComputeCheck](https://computecheck.com/cloud-storage-egress-fees/) puts five stores side by side per GB. Google Cloud is at $0.12, AWS S3 at $0.09, Azure Blob at $0.087, Backblaze B2 at $0.01 and R2 at $0. Read it as a saving on delivery only.
Serve 10 TB a month from S3 and that means about $900 in egress that R2 never bills, but the operation charges still arrive.
### Per-domain multiplication and feature gating
When a client outgrows the cap on rule counts, such as how many firewall or page rules a zone may hold, the upgrade lands on that one domain, not on the account.
**Ten domains means ten separate bills**, because every domain carries its own plan and its own add-ons, and a flat per-client fee hides which one is driving the total.
You can automate usage alerts. [Activepieces](https://www.activepieces.com) can post to a channel when a meter crosses a threshold, and it bills the run, not the steps inside it: 1 credit per flow run, with 1,000 credits a month and unlimited flows on its Free plan.
A ten-step check-compare-notify flow costs the same as a two-step one, so the domain's owner sees the overage mid-month and not on the invoice, and nobody has to trim the alert to keep the bill down.
## Cloudflare against Fastly, Akamai, AWS CloudFront and Bunny
Only Cloudflare, of these five, leaves standard cached traffic unmetered per gigabyte, so its overages come from add-ons and other meters, while the other four can grow with traffic alone.
The table below, checked against each vendor's public pricing pages in November 2026, shows where each provider puts its charges.
| Provider | Pricing model | Free tier | Bandwidth charge | Included security | Support tier |
|---|---|---|---|---|---|
| Cloudflare | Flat per-domain plans, plus meters on some products | Permanent free plan | No per-GB charge on standard cached traffic | Basic DDoS protection; fuller WAF rules on paid plans | Community only on free; tickets on paid; named support at enterprise |
| Fastly | Usage-based | Limited entry offer | Per-GB, by region | Core protection; advanced products sold separately | Paid support packages |
| Akamai | Contract and commit | None self-serve | Per-GB under negotiated terms | Sold as separate products | Contracted support |
| CloudFront | Usage-based | Monthly allowance | Per-GB, by region | Basic DDoS protection; WAF billed separately | AWS support plans |
| Bunny | Usage-based | Trial period | Per-GB, by region | Basic DDoS protection; extras priced separately | Ticket-based |
A usage-based provider wins when traffic is small and spiky, or when one client needs a single feature and shouldn't carry a plan sized for ten. You pay for what that client actually pulls.
The cost is that a viral month lands on the invoice, so each client's meter needs a ceiling you've agreed in writing.
### When Cloudflare's flat plans win
Flat plans win when you host many client domains with steady or growing traffic. Each client's CDN cost is known before the month starts, and that's what you can put on a retainer.
Watch the shared account. Any add-on or meter enabled for one client is billed to everyone unless you split it out, so the client who needs the dearer feature should pay for it.
## How to choose a Cloudflare plan without overpaying
Move a client up only when a named feature forces it, and bill that client for the move. Everyone else stays where they are. Run each site through the same sequence:
1. Start the site on Free and run it for a billing cycle, so the usage meters show what it consumes before you commit to anything.
2. Write down the specific feature that Free can't give you. If you can't name one, the site has no reason to upgrade.
3. Price the cheapest paid plan that unlocks that feature, then check whether a metered add-on on the lower plan does the same job for less.
4. Compare annual and monthly billing. Monthly costs noticeably more for the same plan, so if the client will still be here in a year, annual billing is a discount you can pass on or keep as margin.
5. Ask for an Enterprise quote only when the feature you named exists on Enterprise alone. A quote for anything else is a sales call that ends with you paying for capacity you won't use.
### When a Cloudflare upgrade is worth paying for
When someone outside your team requires it, a trigger is worth paying for: a client's contract, an auditor, or a support commitment you have promised to keep.
Put the cost on that client's account or invoice, not in the shared pool.
Three reasons to upgrade look plausible and usually aren't:
- A plan name that sounds safer than the one you have.
- A feature you might want someday.
- One client's need being used to justify upgrading every site on the account.
The last one is the quiet cross-subsidy: the other clients pay for a feature they never use. Any upgrade that can't be tied to a named feature and a named payer should wait.
## Frequently asked questions
Every budget question comes back to who pays for what, and the same few decide whether a budget holds.
The answers are kept short and carry no price figures, because plan prices change and the pricing page is the source to check before you invoice anyone.
Is Cloudflare really free? Yes, the Free plan is a real plan and not a trial, and you can run a site on it without a time limit.
What it doesn't include is the plan-gated features and higher usage limits, so the cost shows up when a client needs one of them. Price that upgrade to whoever needs the feature.
### Does Cloudflare charge for bandwidth?
For ordinary proxied traffic through the CDN, it generally doesn't bill per gigabyte on the standard plans. Usage-metered products are different: Workers requests, stored objects and operations on R2 (Cloudflare's object storage) are billed on their own meters.
A busy bucket can still produce a bill, because R2 doesn't charge egress but does charge for storage and operations. Check which meter each product runs on before you quote a flat monthly fee.
### Can I downgrade a Cloudflare plan mid-term?
You can usually move to a lower plan, but don't assume a refund of the unused period. Paid add-ons tend to follow their own billing cycles, so cancel them separately.
Before you promise a client a mid-term saving, read the current terms and your renewal date. On a shared account, one forgotten add-on keeps billing and quietly lands on whoever holds the card.
Do I need a plan for each domain? Yes, plans attach to individual zones (a zone is one domain), not to the account as a whole. Ten client domains means ten plan decisions, and a paid plan on one doesn't cover the others.
Keep a per-domain ledger so the client who needs the upgrade is the client who pays for it.
How do I get an Enterprise quote? Go through Cloudflare's sales contact form, because Enterprise is quoted individually and isn't a self-serve checkout.
Arrive with a list of the features you need, your domain count and expected traffic. The more precisely you can name the payer and the feature, the less you'll pay for capacity you won't use.
## Related reading
- [Hugging Face Pricing 2026: Plans and Usage Costs](https://www.activepieces.com/blog/hugging-face-pricing-2026-plans-and-usage-costs)
- [Activepieces Credits: Pricing and Usage (2026 Guide)](https://www.activepieces.com/blog/activepieces-credits-pricing-and-usage-2026-guide)
- [Vellum AI Pricing in 2026 by Seats, Usage and Tokens](https://www.activepieces.com/blog/vellum-ai-pricing-in-2026-by-seats-usage-and-tokens)
## References
- [ComputeCheck](https://computecheck.com/cloud-storage-egress-fees/)
- [WP WAF Manager](https://www.wpwafmanager.com/docs/main/general/cloudflare-free-plan-limitations/)
- [Answer Overflow](https://www.answeroverflow.com/m/1402150142726897766)