Heroku to AWS in one command, with an agent doing the work

Moving off Heroku is rarely a technical problem. Heroku gives you a way of working: push, review app, add-on, rollback. AWS gives you primitives. Teams budget for moving the workloads, then lose six weeks rebuilding the workflow around them.

In this session, Romaric and Guillaume walk through migrating from Heroku to AWS, and how Qovery keeps the Heroku developer experience while running on your own cloud. Guillaume starts with what teams actually pay for on Heroku: five building blocks, including deploys with a simple git push, review apps for every pull request, managed add-ons, rollbacks, and one-off dynos for debugging. He then covers the limits that usually trigger a migration: the 30-second request timeout, the restricted choice of regions (US or Europe) and the data residency issues that come with it, private networking through a VPC that requires an Enterprise plan Heroku no longer sells, and multi-tenant SaaS setups that need one environment per client. Finally, the live demo migrates a Heroku app (web, worker, cron job, PostgreSQL and Redis) to Qovery on AWS with a single command, with provisioning and configuration fully automated.

00:00 Intro and welcome

03:26 About Qovery

05:52 Heroku's five building blocks

11:27 Heroku limits and why teams leave

17:21 A guided migration approach

22:19 Live demo: migrating an app

28:23 Environment variables, secrets and shell access

33:54 Infrastructure in your own cloud

48:21 Database migration

52:30 Next steps and resources