A Practical Proposal for the Sora 2 Team: Release Open Weights Before the Product Sunsets
OpenAI’s official discontinuation notice is clear: the Sora web and app experiences were discontinued on April 26, 2026, and the Sora API is scheduled to be discontinued on September 24, 2026. That creates a serious gap for creators, researchers, and small studios who have already built workflows around the model.
This post is a respectful proposal, not a complaint. The idea is simple: before Sora 2 disappears from the hosted product stack, consider releasing an open-weight or self-hostable version of the model family, or a carefully scoped subset of it, so the creative ecosystem does not lose access entirely.
Sora has already shown that video generation can be more than a novelty. For many users, it became a tool for concept art, previsualization, storyboarding, prototyping, social video, and rapid creative iteration. When a tool like that is removed from public availability, the loss is not only technical. It also affects workflows, communities, learning, and the momentum of independent creators.
A practical open-weight release would not need to be a full one-size-fits-all dump of the entire production stack. It could follow a staged model family approach:
- Sora 2 Lite for local experimentation and lower-memory systems
- Sora 2 Fast for quick previews and lightweight iteration
- Sora 2 Pro for stronger fidelity and more demanding workloads
- Sora 2 Turbo for optimized inference paths
- Sora 2.x updates for measured improvements over time, such as v2.1, v2.2, v2.3, v2.5, and eventually v3
That kind of release strategy would help preserve continuity. It would let creators keep using Sora locally at home or on a studio machine, while allowing OpenAI to continue focusing on higher-level hosted offerings, safety research, and future frontier systems.
The strongest argument for this approach is not sentiment. It is continuity. Creative tools do real work. People build habits, libraries, prompt systems, style references, editing pipelines, and production schedules around them. If a model is shut down without a migration path, the result is immediate disruption. Independent artists, small teams, educators, and experimental creators are usually the first to lose access.
A self-hostable or open-weight Sora would also reduce pressure on centralized infrastructure. If some users can run the model locally, the hosted service is no longer the only bottleneck. That matters for cost, scalability, and long-term resilience. It also aligns with a broader industry trend: OpenAI has already released open-weight models under a permissive Apache 2.0 license, including gpt-oss models intended for broad use and self-hosted deployment. That precedent shows that open weights are not incompatible with OpenAI’s technical direction.
This proposal is not asking OpenAI to give away everything in a way that removes oversight or responsibility. It is asking for a balanced release model. OpenAI could define usage boundaries, provide safety guidance, publish recommended hardware requirements, and ship regular minor updates. That would be enough to preserve the creative value of the model while still respecting operational realities.
There is also a strategic benefit. A controlled open-weight release would build trust. It would show that OpenAI recognizes not only the value of product launches, but also the value of long-term access for the people who adopt and support a model early. Creators remember when a platform helps them. They also remember when it disappears.
If Sora 2 must sunset as a hosted service, then an open-weight or locally runnable version would be the most constructive outcome. It would keep the model alive in the hands of the community, prevent a hard stop in creative workflows, and allow Sora’s technical legacy to continue evolving outside a single subscription or API endpoint.
In short: if the hosted product must end, the weights should not. Let the creative ecosystem keep building, testing, improving, and sharing. That is how a model becomes more than a product. It becomes infrastructure for imagination.