Cloudflare Sales says there are Egress Fees on Workers
A few hours ago I had a call with a CF sales team about a project and they said two things that got me really confused. For context, this is what we are planning:
- About 8 worker scripts deployed
- About 12 billion requests per month across those workers
- About 120 billion CPU ms
- About 20PB data transfer per month overall
- That we plan to use Workers Paid as we have no need for the extra stuff on Workers for platforms at this time.
Based on that, the Cloudflare sales team told us 2 things:
1) That we should not run out application in a CF Pro or Business plan due to the self-service platform limits.
2) If we go to the Enterprise plan, then we WILL be charged egress fees for data that goes through Workers and
On 1) The docs on Workers paid limits says:
- We can have 500 workers, more than the 8 we need.
- There is no limit on requests, more than the 12 billion we need.
- 30s cpu time/request, more than the 10ms we need.
- No mention of data transfer caps.
On 2) there is a lot of buzz about CF lifting egress fees on workers circa Nov 2021, there is a blog post about the lift and there is no mention of such fees in the workers pricing page. My understanding was thus that there are no data transfer fees of any kind on workers.
I would love some help with two questions:
1) What are these hidden esoteric limits they are talking about that would prevent us from running our workload on Workers Paid with CF Pro/Business? (Or are they just trying to create a problem to sell Enterprise?)
2) Are there or are there not data transfer fees on workers?
3 Replies
Most of this sounds like sales teams just trying to scare you.
1. They don’t exist. There are no limits specifically with Workers that exist on paygo plans that get removed with Enterprise. Like with all Cloudflare things, enterprise traffic may be prioritised, especially in more exotic regions, but that’s it. There are a few other edge-cases like getting a dedicated IP via Aegis for Workers only available with enterprise, but these aren’t relevant for almost all apps.
2. Egress with Cloudflare is a funny thing. In all of their marketing you will see “no egress”, “aws egress so high”, etc. but the second you sign an enterprise agreement you are going to be bound by that agreement, and every enterprise CF contract I’m aware of includes egress fees.
Frankly I would stick with business plan unless you need a specific enterprise-only feature. My business is an ent customer and we use features like extended load balancers, spectrum, etc. but we still pay as you go for Workers because it just makes more sense for us.
(This ignores the support and SLAs you’d get with an enterprise contract, but I don’t imagine that’s what you’re asking about here)
Thank you for your answer, this is all very good to know.
Not having SLAs might be a bit tough but I guess it is what it is.
The sales representatives even mentioned whole accounts being blocked for going over those "limits". It's tough to decide to deploy something with this much uncertainty being seeded by the employees themselves.
Assuming the traffic is legit and not abusive/illegal/breaking tos, there’s effectively zero chance the account would be blocked.
You might get sales outreach if you’re pushing high numbers, but outright blocking for this wouldn’t happen.