topic/automatic-model-routing
Developers stop choosing image models manually
DAM Cowboy · W38 · September 2026
Cloudinary's new routing layer selects generative image models automatically based on prompt characteristics. Every few weeks a new model (FLUX, Recraft, Ideogram) claims superiority at some task, and developers spend cycles benchmarking instead of building. Automatic routing offloads that decision to the platform. For DAM teams managing derivative generation, this pattern suggests a future where transformation pipelines select their own tools. The cost is opacity; the benefit is not maintaining a model comparison spreadsheet.
Also in this issue
- agent-loopsWhat makes an agent loop useful?
- iptc-ibc-trustTrust, story objects, and agentic production at IBC 2026
- dam-vs-cmsDigital asset management versus content management
- lightroom-preview-rebuildRebuild Lightroom previews to save space and confirm integrity
- view-transition-apiButtery-smooth image gallery transitions with the View Transition API
DAM Cowboy is published by Stacks, a DAM consultancy. We summarise industry news here; we do not report it, and the original source is linked above.
