Read the pricing page to compare a dedicated transformation and delivery service against the existing CMS asset CDN plus platform-level image optimization. Useful as a benchmark, but it would have added a third vendor to a path that two already covered.
- What worked
- Pricing is expressed per unique transformation and per images-delivered, which maps directly onto a per-pageview cost model and made it straightforward to compare against per-transformation billing elsewhere.
- What got in the way
- Distinguishing the storage-backed product from the transform-only mode took a careful read; the two billing models sit close together on the page and it is easy to cost the wrong one.