Heroku to AWS in an hour.
Fully automated.
One command. An agent reads your repository and deploys it into the AWS account you already own - after you approve the plan.
Teams migrating with Qovery may be eligible for AWS migration credits through our ISV Accelerate partnership.
“We migrated our whole staging environment with a single prompt. Production was a one-click clone of staging. Once the tests gave us confidence we moved DNS off Heroku - we have been running production on our own cloud with Qovery ever since.”
“We liked the Heroku experience, and we knew AWS meant skills and effort we did not have spare - that is why we kept putting the migration off. We do not regret doing it with Qovery. Deployments that took me over two hours now take 30 minutes.”
Three steps, then the agent does it.
Your side takes about five minutes. Everything after that is automated.
- 01
A CloudFormation stack provisions the network and an EKS cluster in your own account - about twenty minutes, and nothing leaves your boundary. Qovery gets a role you can read, scope down or revoke. Talk to a migration engineer before you connect anything.
- 02
One command teaches your coding agent how to read the repository - a Procfile, a Dockerfile, a buildpack, a set of config vars - and describe the deployment in Qovery’s own terms. Nothing is deployed at this point. You are only giving the agent the vocabulary.
- 03
The agent detects every service, writes a Dockerfile where one is missing, maps your Heroku config vars to Qovery variables and secrets, and shows you the plan. You approve it before a single resource is created - and your Heroku Postgres stays where it is, connected over the network, so you validate against real data before migrating a byte.
- 04Optional
Take this first or last - some teams want it as step zero, before they connect anything. A Qovery staff solution engineer reviews the cluster setup and environment layout with your team, then goes through the practices that keep the estate cheap and quiet: node sizing and Spot policy, autoscaling thresholds, preview-environment lifetimes, secret scoping and how to promote the same artifact between stages.
- network
- your VPC, three fixed egress IPs
- cluster
- EKS, in your region
- access
- a role scoped to Qovery
Works with any coding agent that reads skills. Nothing is deployed at this point.
web Node.js 20 Dockerfile generated worker Node.js 20 detected from Procfile scheduler cron 2 jobs database PostgreSQL 15 connected remotely
Nothing has been created yet. You approve the plan first.
- cluster
- node sizing, Spot policy, autoscaling
- workflow
- stages, approval gates, preview TTLs
- access
- secret scoping, roles per environment
From there it is automatic. Your apps come up running and live on AWS, reachable on a public URL - while the Heroku stack keeps serving traffic untouched.
You pay AWS. Usually a lot less.
Heroku charges you for dyno hours. AWS charges you for what you use - and as its customer you get Savings Plans, Reserved Instances, Graviton and Spot, none of which exist on a dyno-hour bill.
Moving a workload off Heroku onto AWS usually cuts infrastructure cost - up to 60% for the same workload that was running on Heroku.
* Depends on your dyno counts and sizes, add-ons, data volume and region. A migration engineer will model your estate against the equivalent AWS shape before you commit to anything.
What you can do on AWS that a dyno bill cannot.
A dyno is billed at list price, per hour, in fixed sizes. The moment the workload runs in your own AWS account, three levers open up that have no equivalent on Heroku.
Savings Plans and Reserved Instances
- Commit to a level of compute for one or three years and the same capacity costs materially less than on-demand. Heroku has no commitment tier to buy - you pay list for every dyno hour, forever. Qovery sizes the node groups; the commitment is made in your account, on your terms, and it applies to everything running there rather than to one app.
Graviton, for the same code
- AWS's ARM instances generally give better price-performance than the x86 equivalent on ordinary web and worker loads. The agent builds your image for arm64 and Qovery schedules the node group onto Graviton, so this is a build-target change rather than a rewrite. On Heroku the underlying CPU is not something you get to choose.
Spot capacity for interruptible work
- Batch jobs, queue workers and preview environments tolerate interruption; a checkout endpoint does not. Qovery keeps web services on on-demand nodes and places the interruptible pools on Spot, which is exactly the split a dyno-hour bill cannot express because every dyno costs the same regardless of how much it matters.
Our control plane. Your account, your bill.
Qovery sits above the infrastructure and never owns it. Every cluster, database and bucket is provisioned inside the AWS account you already hold - AWS invoices you directly.
- We do not take a cut of your AWS spend. A flat subscription, whether your bill is $2k or $200k.
- We push it the other way: idle nodes, oversized requests and preview environments left running get flagged so you stop paying for them.
- Heroku and the PaaS successors run all of this in their account. Qovery runs it in yours.
Not sure which AWS services fit your workload? A solution engineer will map it with you.
CONTROL PLANEStop paying Qovery and the stack keeps running - the manifests and qovery/qovery Terraform are already in your account.
Your first app on AWS,
live within the hour.
Any commercial AWS region, with multi-region and multi-cluster from one control plane. Nothing you do here touches your existing Heroku stack until you decide to move the domain.
Qovery is an AWS ISV Accelerate partner, available on AWS Marketplace. Spend transacts through your existing AWS agreement and counts toward an Enterprise Discount Program commitment.
View on AWS Marketplace →Heroku to AWS
Something not covered here? Talk to a migration engineer - they have done this on estates larger than yours.