Model lifecycle and deprecation
How models are added, paused and removed on Renderly, and how much notice you receive before a model you use goes away.
Last updated:
Availability states
- Available: the model has a verified price and accepts new requests.
- Listed but unavailable: the model stays visible for discovery while creation is paused, for example while its price or settings are verified again.
- Removed: the model no longer accepts new requests. Completed results stay available for their normal retention period.
Notice before removal
Before removing a model that has API usage, Renderly gives at least 14 days notice in the changelog.
A shorter notice is possible only when the model is withdrawn by the provider that runs it, or when a model must be removed for safety, security or legal reasons. In those cases notice is published as soon as practical.
New versions, settings and prices
A new version from a model maker is added as a separate catalogue entry with its own model ID, so an integration keeps using the version it was built for.
Read the current input contract from the catalogue before building against a model. If a model’s settings change, the new contract is verified before the model accepts requests again.
Prices can change. A job is never charged more than the quote you accepted; a price increase requires a new quote.
Plan for change
- Read model availability from the catalogue instead of hard-coding it.
- Keep a tested fallback model for critical workflows.
- Check the changelog for removal notices.