Heroku’s abrupt shift to a sustaining engineering model has rattled developers. On Feb 6, the platform’s blog declared a pivot away from new features toward stability, security and support, and barred Enterprise accounts for new customers. The language feels like a public retreat into maintenance mode, sparking confusion across the community.

Yet mid‑March saw tangible changes: slug sizes grew, SSL provisioning ran more often, and the entire CLI was rebuilt. Even the Head of Product repeated the “sustaining engineering” mantra, promising new features that align with the goal. The contradiction between maintenance rhetoric and fresh releases has left teams uncertain about Heroku’s future roadmap.

The Judoscale team, long‑time Heroku users, called on leadership for clarity. They ask whether the platform is moving toward a smaller, direct‑billing focus or exiting major platform investment. In recent Ruby conferences, several teams already plan migrations, underscoring the urgency for a transparent strategy.

Without a public roadmap, developers face a hard decision: continue relying on a platform that may only fix bugs or shift to alternatives like Fly.io or Render. Heroku’s next move will shape the fate of countless Ruby‑on‑Rails applications that still depend on its simplicity and managed services.