OpenAI didn't sunset Sora. It amputated it.

On September 24, every production workflow calling the Sora Videos API or a Sora model alias stopped working. The deprecation notice included no migration path and no recommended alternative. For enterprise teams on managed OpenAI contracts, the practical gap is the documentation: OpenAI didn't say "use this instead." The support burden landed on developers.

This is the second Sora funeral this year. The consumer app — the TikTok-style feed that hit 3.3 million downloads in November 2025 — was shut down in April after downloads collapsed to 1.1 million and total in-app revenue stalled at roughly $2.1 million. A reported $1 billion Disney licensing deal died with it. Now the developer product is gone too.

The numbers explain the decision

$2.1 million in lifetime consumer revenue against the compute cost of serving video generation is not a business; it's an experiment that failed to convert. Sora 2 was also slow — 50 to 80 seconds per 1080p clip — which made it a poor fit for the production pipelines that might have paid real money.

Inside OpenAI, the explanation is focus. Reporting points to compute being redirected toward enterprise coding tools and a ChatGPT super-app that consolidates the company's products. Video generation didn't make the cut. Sora continues as an internal research project aimed at world models for robotics — the research thread survives, the product doesn't.

What builders should do

If you were on the Sora API, the realistic alternatives are Runway's Gen-4 Turbo, Kling's v2 Pro, or ByteDance's Seedance. Expect friction: pricing structures, prompt formats, and resolution options all differ from the Sora 2 spec. Budget a migration week, not an afternoon.

The larger lesson is about platform risk. When a lab's priorities shift, developer products die — and the labs with the most shifting priorities are the biggest ones. Diversifying across two video providers stopped being optional the day this notice went out.

Sources

  1. [1] pondero.aiRead source
  2. [2] 9to5google.comRead source