Help with TOS compliant structure

Hi, I was hoping to get some help from the community and a CF rep. I host a community website which is a map. The map is essentially a DZI image pyramid, which is about 350k individual Jpgs, each averages less than a MB. Then I have multiple versions of the map. So total, about 1 million images, and 1 Tb of data stored.

However, the 350k images of the main map are by far, the most commonly returned images. The other versions are seldom used for nostalgia. That map is about 350gb total.

The thing is, the transfer rates are very high, as the site sees significant traffic. I'm a solo dev, and the site is not monetised as it's a community resource.

I estimate the usage, with the current popularity, to be something along the high end of:

- 1Tb total storage in R2 at about 1 million files

- 13Tb a day of bandwidth worldwide via CDN / Cache

- 60 Million daily requests

If it makes any difference, the images are immutable, and can be held in browser & Edge for a very long TTL.

This is why I'm concerned about the costs. My desired architecture would be all CF based for the simplicity and protection. This would include the paid services of:

- Domain

- Email routing

- Workers

- Pages

- R2

- Tiered Cache

- CDN

The full route for data would be, page served via a worker page, then get requests for images from:

R2 > Teired Cache > CDN > User

Based on the specific TOS and this blog posts with examples, it seems as though this is permissible so long as I'm paying for a CF service to host it

From this CF blog

>we got rid of the antiquated HTML vs. non-HTML construct, which was far too broad. Finally, we made it clear that customers can serve video and other large files using the CDN so long as that content is hosted by a Cloudflare service like Stream, Images, or R2

Is anyone serving a full static website like this? And am I correct in the wording of the TOS and blog post?