Heroku to Azure in an hour.
Fully automated.
One command. An agent reads your repository and deploys it into the Azure subscription you already own - after you approve the plan.
“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 the cloud 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 service principal provisions the network and an AKS cluster in your own subscription - 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
- AKS, 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 Azure, reachable on a public URL - while the Heroku stack keeps serving traffic untouched.
You pay Azure. And it counts toward your commitment.
Heroku charges you for dyno hours, and none of it counts toward anything. Azure charges you for what you use - and the spend draws down your Enterprise Agreement or MACC commitment like any other Azure workload.
Moving a workload off Heroku onto Azure 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 Azure shape before you commit to anything.
Why Azure is different if you are already a Microsoft shop.
For most teams the Azure argument is not really about compute pricing. It is that the money and the identity are already there, and Heroku sits outside both.
Spend counts toward your EA or MACC
- If your organisation has an Enterprise Agreement or a Microsoft Azure Consumption Commitment, you have already promised Microsoft a level of spend. Workloads running on Heroku contribute nothing toward it - you are paying Salesforce while separately owing Microsoft a commitment. Move them to your own subscription and the same compute draws down an obligation you are committed to regardless.
Entra ID decides who deploys where
- Access is governed by the directory you already run. SAML SSO against Entra ID, your existing groups, and conditional access policies determine who can deploy to production - rather than a separate list of Heroku collaborators that no one reconciles against leavers.
Reservations and the Azure savings plan for compute
- Reserved instances for the steady-state footprint, the savings plan for compute where the shape moves around, and Spot for interruptible pools. All three are priced against your subscription. On a dyno bill there is nothing to reserve and nothing to discount.
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 Azure subscription you already hold - Azure invoices you directly.
- We do not take a cut of your Azure 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 Azure 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 Azure,
live within the hour.
Any Azure 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.
Heroku to Azure
Something not covered here? Talk to a migration engineer - they have done this on estates larger than yours.