You're right, and I apologize for the inaccurate information. Cloudflare Images does support on-the-fly transformations via URL parameters.
In fact, img-src.io's infrastructure runs on Cloudflare, and I initially considered wrapping Cloudflare Images for the transformation layer. However, the cost of scaling became prohibitive—if 100k free-tier users each transform 1k images, I'd be bankrupt. So I built a custom transformation service using libvips (which Cloudflare Images itself uses under the hood) and deployed it on Cloudflare Containers.
To be clear, this service isn't targeting folks like yourself who can spin up image transformation infrastructure in their sleep. It's for developers who find infrastructure setup tedious or daunting and just want simple image transformation with CDN caching out of the box.
In fact, img-src.io's infrastructure runs on Cloudflare, and I initially considered wrapping Cloudflare Images for the transformation layer. However, the cost of scaling became prohibitive—if 100k free-tier users each transform 1k images, I'd be bankrupt. So I built a custom transformation service using libvips (which Cloudflare Images itself uses under the hood) and deployed it on Cloudflare Containers.
You can see the architecture here: https://docs.img-src.io/introduction#how-it-works
To be clear, this service isn't targeting folks like yourself who can spin up image transformation infrastructure in their sleep. It's for developers who find infrastructure setup tedious or daunting and just want simple image transformation with CDN caching out of the box.
Thanks for the feedback