Heroku has changed course. Does your app need to leave?
Heroku now prioritises stability and security over new features and no longer offers Enterprise contracts to new customers. There is no rush, but an exit plan is worth having.
Plenty of startups and internal systems were born on Heroku. In 2026, the platform entered a new phase.
What Heroku announced
On 6 February, Heroku announced a move to a "sustaining engineering" model, focused on stability, security, reliability and support rather than new features. The company says nothing changes for existing users: pricing, billing and day-to-day use stay the same for credit-card customers. Enterprise contracts are no longer offered to new customers, while existing ones remain valid and can be renewed.
Nobody has to leave tomorrow. What changed is the horizon.
Signs it's time to plan your exit
- Your app depends on features the platform is unlikely to prioritise.
- A large customer asks for hosting on AWS or Google Cloud, a data agreement or a security questionnaire.
- Your company would need a new enterprise contract, which is no longer offered.
- The bill grows with usage and nobody can predict next month.
If none of these signs show up, staying is a reasonable choice, as long as there is a plan for the day you need to move.
How to build an exit plan without rushing
- Inventory: apps, databases, add-ons, environment variables and scheduled jobs.
- Destination: AWS or Google Cloud, based on your team's skills and what your customers require.
- Infrastructure as code, so the new environment is repeatable and documented.
- Parallel testing, with the new system running alongside the current one.
- A supervised switchover, with a defined way back.
Migration with a written plan
When we migrate apps to AWS and Google Cloud, you get a written plan before anything changes. We run parallel tests, supervise the switchover and keep the code and accounts in your company's name.