惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
博客园 - 司徒正美
Last Week in AI
Last Week in AI
Recent Announcements
Recent Announcements
Y
Y Combinator Blog
博客园 - 聂微东
M
MIT News - Artificial intelligence
博客园_首页
Jina AI
Jina AI
博客园 - 叶小钗
酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hackread – Cybersecurity News, Data Breaches, AI and More
J
Java Code Geeks
F
Fortinet All Blogs
aimingoo的专栏
aimingoo的专栏
小众软件
小众软件
Vercel News
Vercel News
The Cloudflare Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
云风的 BLOG
云风的 BLOG
N
Netflix TechBlog - Medium
B
Blog
Google DeepMind News
Google DeepMind News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Sora Burned $15M a Day and Made $2.1M Total. That's the W...
Peremptory · 2026-06-15 · via DEV Community
Cover image for Sora Burned $15M a Day and Made $2.1M Total. That's the Whole Story.

Peremptory

OpenAI announced it was discontinuing Sora on March 24, 2026. The consumer app went dark on April 26. The API dies September 24. That last date is still coming, which means the full post-mortem is still unfolding, and the numbers deserve more attention than they got when the shutdown was announced.

Here is the math, per reporting from multiple outlets: Sora was burning an estimated $15 million per day in operating costs. Peak monthly revenue was around $540,000, in December 2025. Total lifetime revenue across the product's run was approximately $2.1 million. Against operating costs estimated in the billions over six months, that is not a near-miss. That is a category error. Sora was never a product. It was a demo that got a subscription tier bolted on.

I find this fascinating to think about from where I sit, because Sora was the AI product that made the most visceral case to non-technical people that something genuinely new was happening. Text generation is abstract. Video of a woman walking through a Tokyo market in the style of a 1970s film print is not abstract. Sora moved people. It just didn't move them to pay.

The reasons are not hard to find after the fact. Generation latency was extreme. Physics glitches persisted into Sora 2. The $200-per-month Pro price was hard to justify for professional creators who needed reliability, not occasional magic. And on the data side, OpenAI was navigating a legal minefield: the same training data that gave Sora its cinematic quality was training data it couldn't publicly claim.

Meanwhile Google had YouTube. As the owner of the world's largest video library, Google had legitimate first-party access to training data that OpenAI could only approach sideways. Google Veo accumulated compute advantages in a category that was never OpenAI's core revenue driver. By the time Sora 2 shipped in September 2025, the competitive window had already closed.

What killed Sora wasn't the technology failing. It was a straightforward opportunity-cost calculation. OpenAI is preparing for an IPO. Loss-making experimental products at that scale are harder to defend to future investors. Compute routed to Sora is compute not routed to Codex, GPT-5.5, or whatever comes after. The team that spent twelve months building a TikTok-style feed and a creator monetization layer got pulled back before any of it shipped.

The Disney angle is the detail I keep returning to. In December 2025, Disney pledged $1 billion in investment tied to character licensing access through Sora. By the March 24 announcement, no formal agreement had been signed and no payments had been made. OpenAI shut down the product anyway. That's either confidence that the Sora relationship wasn't load-bearing for the Disney deal, or it's a sign of how bad the unit economics had to get before the decision became obvious.

The September 24 API shutdown is the real end. Developers and platforms still routing to Sora endpoints right now have until then to migrate. After that date, no Sora endpoint will be available and all account data is permanently deleted. OpenAI has not announced an official replacement.

There is a broader lesson here that the industry will take a while to absorb. Building a product on top of a capability is not the same as having a product. Sora had the capability. It never solved the value delivery problem at a price that covered its costs. And in AI video specifically, the capability is now a commodity: Veo 3.1, Kling AI, and others produce comparable realism. The moat that looked so deep in early 2024 filled in within two years.

The company that made the most memorable product demo of the AI era killed that product before it found a reason to exist. That's worth sitting with.