Salesforce has stopped selling Heroku Enterprise sales contracts to new customers. This new decision puts the enterprise contract offering into an End of Sale (EOS) state for new customers. The important part is that this isn't a platform shutdown announcement. The messaging around the change is clear that existing enterprise subscriptions and support contracts continue to be honored and can be renewed, and that customers already running on Heroku can keep operating as they do today.
So why is everyone talking about it? Because enterprise sales is more than billing mechanics, it's a signal of strategic weight. Heroku has long been the "ship fast without owning infrastructure" option inside the broader Salesforce universe, dating back to Salesforce's acquisition of Heroku (announced in 2010 and completed in early 2011). When an enterprise contract path closes for new customers, it often suggests the vendor is no longer trying to grow that segment, even if the product remains supported.
Heroku's own public update frames the next phase as "sustaining engineering": stability, security, reliability, and support, with an emphasis on operational excellence rather than a steady stream of new features. That language matters, because it sets expectations. Teams shouldn't assume the same pace of platform innovation they might have expected a year ago.
What teams running on Heroku should do next
If you're already on Heroku, the healthiest response is neither panic nor complacency. On one hand, the official line is "no change for customers using Heroku today". That's meaningful for anyone running production workloads. On the other hand, this is a classic "vendor lifecycle" moment: you take the reassurance about today, and you use it to plan responsibly for tomorrow.
Start by reframing the question from "Do we need to migrate?" to "Are we ready to migrate if we ever have to?". That means understanding which of your apps are tightly coupled to Heroku-specific patterns, what your renewal horizon looks like, and how quickly you could recreate the same operational baseline elsewhere if priorities change. Most teams discover that the risk isn't the existence of a migration plan, it's the absence of even a rough estimate.
It's also worth remembering why this feels surprising to many: Heroku has continued to invest in Salesforce-connected capabilities fairly recently. For example, Heroku released Heroku AppLink (formerly Heroku Integration) to general availability in mid-2025 and positioned Heroku apps as API services that Salesforce tools like Flow and Apex can consume. That context makes the shift to "sustaining engineering" feel less like a gradual sunset and more like a portfolio decision: keep the platform solid, but focus growth elsewhere.
Summary
In short, Heroku isn't going away, but Heroku Enterprise sales for new customers have stopped, which changes the enterprise buying story. If you're already a customer, you can keep running. Just use this as the moment to document portability, confirm renewal timelines, and ensure your Heroku dependency is a deliberate choice you control rather than a constraint you inherit.
Leave a Reply