Between February 5 and May 5, 2026 — 89 days — OpenAI shipped five distinct GPT-5.x variants. Claude Opus 4.6 opened that window. GPT-5.5 Instant closed it. Anthropic, Google, Alibaba, Xiaomi, and DeepSeek matched pace throughout. The Frontier Model Release Velocity Index (FMRVI), published by Digital Applied to track substantive frontier launches across labs, recorded more than 12 releases in Q1 2026 — roughly three per week.
That cadence is the model release treadmill. If your business runs AI in production, it changes how you plan, budget, and build. This article is an orientation hub for six cluster pieces: Five Models in Three Months, Multi-Model Month: April 2026, Deprecation Pressure, Benchmark Inflation, Lock In vs Keep Up, and Architecture That Survives Model Churn.
What is the AI model release treadmill and why does it matter for enterprises?
The model release treadmill describes the structural shift from biannual flagship releases to a weekly cadence. The FMRVI recorded a doubling of release velocity between Q4 2025 and Q1 2026. Each new model is a distinct artifact — different behaviours, prompting requirements, and its own deprecation clock — not a patched version of its predecessor. Evaluation, integration, and validation must now run in weeks. Model selection has become a continuous operational burden.
Deep dive: the GPT-5.x timeline.
What did the 89-day window between February and May 2026 actually look like?
In 89 days, OpenAI shipped GPT-5.3 Instant (March 3), GPT-5.4 (March 5), GPT-5.4 mini (March 18), GPT-5.5 — nicknamed “Spud” — (April 23), and GPT-5.5 Instant (May 5). Claude Opus 4.6 opened the sequence on February 5, making this cross-vendor from day one. The cadence compressed across the window: GPT-5 to GPT-5.2 took 18 weeks; GPT-5.4 to GPT-5.5 took just 7. Each event required enterprise teams to assess regression risk and decide before the next release arrived.
Full timeline: the 89-day release sequence.
Is this just OpenAI, or are all the major labs running at this pace?
It is industry-wide. Anthropic’s Opus cadence compressed from 26 weeks (4 → 4.5) to 10 weeks for each subsequent pair. Google halved its Pro interval from 34 weeks to 13. Alibaba shipped seven Qwen variants in ten weeks — the highest-cadence shipper in Q1 2026 per FMRVI. April 2026 saw Claude Opus 4.7, GPT-5.5, Gemini 3.1 Pro, DeepSeek V4, and Kimi K2 Thinking all arrive within the same month.
Cross-vendor convergence: evaluation window collapse in April 2026.
Why do faster model releases mean faster model deprecations?
Each new release creates pressure to retire its predecessor. Production lifespans that once ran 12–18 months are compressing toward six. OpenAI retired GPT-4o in February 2026 and GPT-5.1 in March. Anthropic announced Claude Sonnet 4 and Opus 4 would reach end-of-life June 15 — approximately 62 days’ notice. Gemini 2.0 Flash shuts down June 1. The faster the treadmill runs, the shorter the runway before a forced migration.
Deprecation and retirement are distinct: deprecation blocks new deployments but leaves existing calls working; retirement removes the endpoint entirely. After retirement, calls either fail or silently activate an unplanned fallback — routing to a different, potentially weaker model — without any deployment-level alert.
Migration checklist and contractual guidance: the six-month shelf life of enterprise AI.
What does a model deprecation actually cost in engineering time?
The API config change — updating the model string in a .env file — takes an afternoon; the rest does not. Prompt revalidation, where every system prompt and few-shot example must be tested against the new model’s behaviour, takes weeks. Add regression testing, schema repair for changed output formats, and compliance re-validation in regulated industries, and the true migration cost is measured in engineering weeks. Most organisations have no AI continuity plan to absorb these costs predictably.
Full breakdown: what deprecation pressure costs in practice.
Why should you stop relying on AI benchmark scores to choose a model?
At today’s release velocity, published benchmarks are structurally outdated before they reach you. GPT-5.5’s safety card compared it to Claude Opus 4.5 — already superseded by Opus 4.7 before the card was published. Scores also suffer from contamination: evaluation data infiltrates training corpora. Kimi K2 self-reported 50 percent on the HLE benchmark; independent testing found 29.4 percent. Intelligence rank and usage rank diverge sharply — a leaderboard position is not a production decision.
Alternatives: when leaderboards mislead.
What is driving the open-source and Chinese lab acceleration — and why does it matter?
Chinese labs are setting pace, not catching up. Xiaomi’s MiMo V2 reached 21 percent of OpenRouter token volume in four months. DeepSeek-V3.2 benchmarks against GPT-5 and Gemini 3.0 Pro as an open-weight model with a reported training cost of $4.6 million. Kimi K2 Thinking was described as a “DeepSeek moment” for Moonshot AI. Open-weight releases add capable new models to your evaluation queue without adding managed deprecation policies: no endpoint removal, no formal notice period.
Independent testing found Kimi K2’s self-reported HLE score of 50 percent was actually 29.4 percent — a gap that illustrates the evaluation burden open-weight models place on your team.
Evaluation window implications: the cross-vendor convergence case study.
How does constant model selection affect your operational budget?
The FMRVI documents compression of enterprise evaluation cycles from six months (2024) to three months (2025) to four weeks (Q2 2026), with no floor yet observed. At four-week cadence, model evaluation becomes a standing operation. FMRVI recommends budgeting three to five percent of total AI spend for evaluation infrastructure and holding ten to fifteen percent as an uncommitted reserve — when a release resets the capability frontier mid-quarter, organisations that can reallocate budget in two weeks outperform those on rigid annual plans.
Strategic budget framing: the enterprise model strategy dilemma.
What are the two strategic choices — and what does each actually cost?
The lock-in posture commits to a specific model version, reducing evaluation overhead but accumulating technical debt toward a forced migration. The keep-up posture chases releases, maximising capability access but converting engineering capacity into a standing upgrade operation. Neither is neutral — provider lock-in is a single-vendor dependency with one remedy, while model lock-in is tight coupling to specific output patterns with a different remedy. Staying put on either eventually forces a migration with no abstraction layer in place.
Full framework: lock-in vs keep-up decision framework.
What architectural patterns reduce the cost of living on the treadmill?
A model abstraction layer — a thin interface between your application code and the provider API — is the most effective starting point, enabling model swaps without codebase refactoring. Pair it with model-agnostic prompt design, a continuous evaluation harness running against a canonical task set of 30–50 production-representative tasks, and staged rollout gates routing a percentage of traffic to a candidate model before full cutover.
Implementation guide: AI architecture that survives model churn.
The sections above frame each dimension of the treadmill problem; below is a navigation guide for where to enter based on your current situation.
Reading Guide: Where to start based on your current situation
Just received a deprecation notice — Deprecation Pressure for migration checklist and vendor questions.
Trying to understand the last 90 days — Five Models in Three Months for the timeline, then Multi-Model Month: April 2026 for the cross-vendor picture.
Presenting this to your board — Lock In vs Keep Up for strategic framing and board-ready language.
Building or refactoring production AI systems — go directly to Architecture That Survives Model Churn.
Making a model selection decision using benchmark scores — read Benchmark Inflation first.
Resource Hub: The Model Release Treadmill Library
Understanding the Treadmill — Evidence and Timeline
- Five Models in Three Months: The 89-day release sequence and why the pace is structurally new.
- Multi-Model Month — April 2026: Cross-vendor convergence and the collapse of evaluation windows.
- Benchmark Inflation: Why published benchmarks are structurally outdated and what to use instead.
Managing the Operational Consequences
- Deprecation Pressure: What model deprecation costs in practice, with migration checklist and contractual guidance.
- Lock In vs Keep Up: Strategic framework for model stability versus capability currency.
- Architecture That Survives Model Churn: Abstraction layers, continuous evaluation harnesses, and staged rollout patterns.
The treadmill is not going to slow down. The competitive dynamic between Western labs and Chinese labs is a feedback loop with no obvious floor. What changes is whether your architecture treats each new release as an emergency or a routine evaluation event.
