Today, Google is shutting off its Imagen 4 API. If any tool in your stack — a logo generator, a content workflow, an internal app — was quietly built on top of it, it doesn't fail gracefully. It just breaks. Hard error, no warning banner, starting today.
This isn't really a story about image generation. It's a story about what happens when your business quietly depends on someone else's roadmap.
The Angst — This Week's Fear
"We built our whole workflow around this tool. What happens when it just... goes away?"
A completely reasonable fear right now. AI moves fast enough that even Google retires major model endpoints inside about a year of launching them. Nobody sends your five-person team a heads-up when the API three tools deep in your stack quietly relies on a model that's being shut down.
What Actually Happened
Google announced back in mid-June that it was deprecating all three Imagen 4 endpoints, with today, August 17, as the shutdown date. That part isn't a surprise if you were watching closely. What matters for most business owners is what's on the other side: the replacement, Gemini 3.1 Flash Image, isn't a simple swap. The API itself works differently, existing prompts don't automatically produce the same output, and depending on your usage, the cost per image can go up.
And this is just the most visible example. The pace of change underneath it is the real story — Google shipped a new Gemini Flash model just three weeks after the last one. Model churn like that is becoming normal, not the exception. Any tool built on top of a specific model is only as stable as that model's shelf life.
The 3-Question Dependency Check
You don't need to track every model deprecation notice yourself. But it's worth knowing, for each tool your business depends on:
- Is this a standalone product, or a thin wrapper on one underlying model?
- Does the vendor have a track record of active, ongoing development — or did they build it once and move on?
- If this tool disappeared tomorrow, do we know what we'd replace it with?
"Active development" is one of the five criteria every tool has to clear before it earns a spot in the Promptory vault — precisely so you're not the one finding out the hard way, on a Monday, that something broke overnight.
List every AI tool your business currently pays for or relies on. For each one, ask your AI assistant: "Is this a standalone product with its own team and roadmap, or is it primarily a wrapper around a single third-party AI model? What would happen to my workflow if that underlying model were discontinued?" It won't catch everything — but it's a fast way to spot your weakest links.