In the past few years there was this blog post[0] that clarified this. It moved the restriction on serving a "disproportionate percentage of pictures, audio files, or other large files" to another part of the TOS dedicated specifically to the CDN part[1] and clarified that, if you're using Cloudflare add-on services Stream, R2 (their S3), or Cloudflare Images, then you won't be at risk of termination.
Comments
I’ve been toying with the idea of implementing a distributed analytics engine on top of Cloudflare workers and DuckDB.
I’m not sure if this goes against the CloudFlare TOS tough (last time I checked they had some provisons against processing images).
In the past few years there was this blog post[0] that clarified this. It moved the restriction on serving a "disproportionate percentage of pictures, audio files, or other large files" to another part of the TOS dedicated specifically to the CDN part[1] and clarified that, if you're using Cloudflare add-on services Stream, R2 (their S3), or Cloudflare Images, then you won't be at risk of termination.
0: https://blog.cloudflare.com/updated-tos/
1: The restriction still exists at https://www.cloudflare.com/service-specific-terms-applicatio... under "Content Delivery Network (Free, Pro, or Business)".
BoilingData does something very similar, except with Lambdas on AWS.
They've already got one: https://developers.cloudflare.com/analytics/analytics-engine...
IMO that’s not really possible because of the size limits of Cloudflare Workers. Neither the WASM nor the Node version are small enough.
I‘m running it on AWS Lambda functions with some success.