On February 6, 2026, Salesforce officially moved Heroku into what they called a "sustaining engineering model." No new features. No new enterprise contracts. Stability and security only.
If you've been building on Heroku, you already felt this coming. The free tier disappeared in 2022. Pricing went up. Performance stagnated. The developer community that once evangelized the platform started looking elsewhere years ago.
The announcement just made it official.
What "sustaining engineering" actually means
Let's be direct about what this means, because Salesforce's messaging is carefully worded to avoid saying the quiet part out loud.
No new features means the platform falls further behind every month. The cloud ecosystem moves fast. When the rest of the market is shipping fast deploys, built-in AI tooling, and transparent billing, a platform in maintenance mode becomes a liability.
No new enterprise contracts means Salesforce is actively discouraging new investment. When the company that owns your infrastructure stops selling it to new customers, that tells you everything about where their priorities are.
The team maintaining Heroku will get smaller over time. Response times will get longer. Edge cases will stop getting fixed. Add-on partners will deprioritize integrations because the user base is shrinking.
This isn't speculation. I've seen this pattern before with IBM Bluemix, VMware's Pivotal Cloud Foundry, and Google App Engine's standard environment. "Sustaining engineering" is how platforms die slowly instead of all at once.
The biggest risk isn't a sudden shutdown. It's the slow degradation that makes migration harder and more expensive every quarter you wait.
Why this happened
Heroku was genuinely revolutionary. Git push to deploy. Dynos that scale with a slider. Add-ons for everything. For the first time, a developer could go from code to production in minutes without touching a server.
Salesforce acquired Heroku in 2010 for $212 million. But over time, the original developer-first philosophy got diluted by enterprise requirements. Compliance features, Salesforce integrations, and corporate overhead took priority over the things that made developers love the platform in the first place.
The final blow wasn't technical. It was strategic. Salesforce decided to redirect engineering investment toward AI and enterprise agents. Heroku's enterprise offering couldn't justify its resources against Salesforce's AI ambitions.
Here's the lesson: Heroku didn't die because it was a bad product. It died because a parent company made a business decision that had nothing to do with the developers using it.
TL;DR: Heroku was killed.
What to look for in your next platform
I've been working with companies migrating off various platforms for years now. Here's what actually matters:
Deploy experience that's at least as good. This is non-negotiable. If moving off Heroku means your deploys go from one command to a 45-minute pipeline configuration, you've solved nothing. Look for GitHub actions native support, automatic SSL, and environments that spin up in seconds.
Transparent pricing. Heroku's original strength was simple pricing. Many alternatives have gone the opposite direction with bandwidth charges, build minute limits, and add-on fees that make your bill unpredictable. You should know what you'll pay before you use it.
A real migration path. Migrating off Heroku involves your app, your database, your environment variables, your add-ons, your custom domains, and your SSL certificates. Some platforms offer assisted migration. Others leave you on your own. The difference between a weekend migration and a three-month project often comes down to how much help you get.
No new lock-in. This is the one most people miss. If you're leaving Heroku because Salesforce made a business decision that affected your infrastructure, make sure you're not walking into the same situation with a new provider. Single-cloud platforms carry the same structural risk. If the company behind your platform gets acquired, pivots, or runs out of funding, you're back to square one. Look for portability.
Real human support when things break. Heroku's support was solid in the early days but degraded over time. When you're running production workloads and something goes wrong at 2am, the difference between an automated response and a real engineer is everything.
How to plan your migration
If you're on Heroku and haven't started planning, now is the time. Not because the platform is shutting down tomorrow, but because migration gets harder the longer you wait.
Start by auditing what you have. How many apps? What databases? Which add-ons? What's your monthly spend? Understanding the full scope prevents surprises.
Set a concrete timeline. "We'll migrate eventually" is how you end up migrating under pressure when Heroku announces the next reduction in service. A plan with milestones keeps the project moving.
Consider getting help. We've migrated companies off multiple platforms and cloud providers at Quave ONE. The difference between a planned migration and a panic migration is months of engineering time and unnecessary stress.
The bigger picture
Heroku's story is worth paying attention to regardless of what platform you're on.
A product that was once the best option for deploying web applications became a liability because a parent company's priorities shifted. The developers who built their businesses on Heroku had no say in that decision.
This is why portability matters. This is why understanding your infrastructure dependencies matters. The question isn't just "what should I migrate to?" It's "how do I make sure I'm never in this position again?"
At Quave ONE, we manage cloud infrastructure across on-premise, AWS, GCP, Azure, and OCI for companies ranging from early-stage startups to public companies with high traffic and complex data requirements. We offer free migration assistance for teams moving off Heroku and other platforms.
If you want to talk through your situation, send us a message.