#
Retirement Notices and Migration
For LTS models, the planned retirement date will be at least six months after we announce deprecation. We publish retirement details in Cloud Docs and notify affected customers where applicable. Notices identify the model, relevant dates, suggested alternatives, and migration guidance when available.
Before final retirement, a model may move to On-Demand status. In that state, active hosting is paused, but customers can request temporary reactivation through a service ticket.
#
What a retirement notice includes
- The model identifier and name
- The announcement date and planned retirement date
- Suggested replacement models
- Migration guidance where available
#
On-Demand status
When a model moves to On-Demand status:
- Active hosting is paused; the model is not continuously loaded on GPU.
- Customers can request temporary reactivation by opening a service ticket.
- On-Demand availability is intended as a bridge during migration, not as a long-term hosting arrangement.
#
Where to check
- Scheduled for Retirement: models with announced retirement dates.
- Decommissioned Models: models no longer available.
- Active Models: current production catalog.