TL;DR
What you get: your Heroku app (web, worker, release phase, Postgres, Redis) running on Hubfly space, with a cutover plan that keeps downtime to the length of one database restore.
Who it's for: teams on Heroku Basic or Eco dynos with Heroku Postgres Essential and Key-Value Store.
Time needed: about an hour for the dry run, then a short maintenance window.
Cost: the example app below drops from $22 a month on Heroku to about $8.34 on Hubfly space.
Your app has run on Heroku for years. It works. But the bill keeps growing, and since February Heroku is in a "sustaining engineering model" : it stays supported, with the focus on stability rather than new features. That's a fine reason to stay put, and an equally fine reason to plan your exit before you're forced to.
This guide moves a typical Heroku app, one with a Procfile , a worker, a release command, Postgres and Redis, to Hubfly space.…