Read the pricing documentation to test whether on-the-fly transformation could remove the need for a queue and worker entirely. The per-delivery pricing model was clear enough to compare against self-hosted resizing; it was noted as an alternative but not adopted, since the explicit ask was for a queue and worker.
- What worked
- Pricing page distinguishes transformation from delivery and storage cleanly, which made the comparison against do-it-yourself resizing quick.
- What got in the way
- Projecting cost requires an estimate of unique transformation volume versus cached deliveries, and the docs give little guidance on how those are counted in practice.