Heroku Is Really Dead This Time, and Here's What Happened

There's a specific kind of death for tech platforms, and it's not the dramatic shutdown everyone expects. It's the slow transition to "sustaining engineering mode"—corporate speak for "we've given up, but we can't actually say that."

That's where Heroku is now. The platform that taught an entire generation of developers what deployment could feel like has officially entered maintenance mode, complete with massive layoffs and a leadership team that's mostly... gone.

The Git Push Heard Round the World

If you weren't building things in the early 2010s, it's hard to explain what Heroku meant. AWS existed, sure, but using it felt like assembling furniture without instructions. Heroku was the first platform where you could connect a GitHub repo and just... have a server. That "git push heroku main" workflow wasn't just convenient—it was magical.

"Heroku was the first platform that really had that magic feeling of linking something to a GitHub repo and the server just kind of exists," tech YouTuber Theo explains in a recent video breaking down the platform's demise. "There's a reason that so many developers that you know, love, and learn from today all learned the way they did on top of Heroku."

That magic came with a generous free tier, which became one of Heroku's defining features. For years, you could spin up hobby projects, experiment with new frameworks, or learn deployment without spending a cent. It was the developer equivalent of a gateway drug—get hooked on the experience, bring it to work, scale up on the paid tiers.

How Salesforce Fumbled the Bag

The trouble started in 2010 when Salesforce acquired Heroku for $212 million. The logic made sense at the time: Salesforce was built on Heroku infrastructure, and buying it was cheaper than migrating off. But that's exactly the problem—Salesforce bought Heroku to solve their own infrastructure needs, not to run a developer platform business.

The free tier died in September 2022, which should have been the first major warning sign. Removing free access from a platform defined by accessibility is like Twitter charging for basic accounts—theoretically possible, but culturally devastating.

Then came the leadership exodus. In July 2024, Heroku CEO Bob Wise opened a search for a new Chief Product Officer because the existing one wanted to step back. By November—just four months later—Wise himself left Salesforce. Losing both your CPO and CEO in a single quarter is basically a death certificate, just on a slow-release timer.

"Losing your CPO and CEO in a four-month window is basically a guarantee of death," Theo notes. Without leadership providing direction, the remaining engineering teams went into "fight or flight mode," building features without a coherent roadmap and getting increasingly close to shipping meaningful updates before—well, before everything stopped.

The layoffs that followed wiped out over half the team, including engineers who were apparently close to bringing back a modernized free tier and introducing features that could have made Heroku competitive again. They were "close to getting to the start of the race," as Theo puts it, "and right before they walked into the track, they decided to just shoot themselves."

The Blog Post That Said Everything and Nothing

Heroku's official blog post about the transition is a masterclass in corporate non-communication. "Heroku remains an actively supported production-ready platform with an emphasis on maintaining quality and operational excellence rather than introducing new features," it reads—as if "we're not building anything new" is somehow reassuring.

What the post doesn't mention: no new enterprise contracts will be offered. Existing enterprise customers are being migrated to credit card billing instead of proper invoices. The platform is effectively in hospice care.

The only new feature announcement? A GitHub Enterprise Server integration that was probably planned months before the transition and posted by a CPO who may not even work there anymore.

Should You Trust Any Free Tier?

Heroku's collapse raises an uncomfortable question: can developers trust free tiers at all? The answer is more nuanced than you'd think, and it comes down to infrastructure models.

Platforms like Vercel, Netlify, and Cloudflare can sustain generous free tiers because they're built on serverless architecture. When you deploy to Vercel, nothing actually runs until someone visits your site. No traffic means no compute costs. Your code just sits in storage waiting to be invoked. That's why preview environments are basically free—they're just bundles of code that only spin up when you click the URL.

"When you deploy something on Vercel, it costs $0 for Vercel," Theo explains. "The only thing that costs money for them effectively is when you actually go to the site."

Traditional server platforms like Heroku are different. When you provision a Heroku dyno, it's running 24/7 whether anyone's using it or not. That's real infrastructure cost that scales with users, not usage. Railway learned this lesson the expensive way—their free tier became unsustainable on Google Cloud Platform, so founder Jake got so frustrated he started racking his own servers to reduce costs.

PlanetScale offers another cautionary tale. Their free tier gave you the same multi-replica MySQL setup as paying customers, which was eating massive costs. When they needed to fix their economics, the free tier was the first thing to go.

The pattern is clear: serverless platforms have structurally sustainable free tiers. Traditional server platforms are making a bet that free users convert to paid at rates that justify the cost. When that bet doesn't pay off—or when new management stops caring—the free tier dies.

What This Means for the Platforms You're Using Right Now

The Heroku story isn't really about one platform dying. It's about what happens when companies get acquired by organizations that don't understand—or care about—the product they bought.

GitHub's trajectory under Microsoft feels eerily similar. Most of the pre-acquisition leadership is gone. The people who remain care deeply, but the institutional culture has shifted. The difference is that Microsoft has, so far, continued investing in GitHub's growth. Salesforce did the opposite with Heroku.

For developers, the lesson is about dependency risk. If you're building on a platform, you need to understand whether its free or cheap tier is structurally sustainable or strategically subsidized. Subsidies end when strategies change. Infrastructure costs are forever.

Heroku pioneered the "git push to deploy" workflow that every modern platform tries to recreate. That innovation mattered. But innovation without sustainable business model and committed leadership is just a ticking clock. And for Heroku, time's up.

—Zara Chen