Meerada · Deprecation Radar

Which models are retiring, when, and what to move to — measured, not guessed · as of 2026-08-29
Tracked retirements
7
Migrate within 90 days
3
ModelRetiresCountdownMove to
sora-api
openai · no direct replacement mapped
2026-09-30 32 days no direct replacement mapped
gpt-4-legacy-snapshots
openai · legacy GPT-4 snapshots sunset
2026-10-15 47 days gpt-5.6-terra gpt-5.6-luna
gemini-2.5-family
google · 2.5 family retires
2026-10-16 48 days gemini-3.6-flash gemini-3.1-pro
qwen-free-dev-tier
alibaba · free dev tier ended
2026-04-15 retired qwen3.7-max
deepseek-chat-legacy
deepseek · legacy chat/reasoner retired
2026-07-24 retired deepseek-v4-flash deepseek-v4-pro
claude-opus-4-1
anthropic · already retired
2026-08-05 retired claude-opus-5 claude-sonnet-5
assistants-api
openai · structural break: migrate to Responses API
2026-08-26 retired responses-api
Facing one of these? Don't guess which replacement holds up on your workload. Run meerada pack on your traffic and get a measured per-cluster gap report — pass/block, cost delta, and the engineer-days to migrate. Content never leaves your environment.