Render to AWS in an hour.
Fully automated.
One command. An agent reads your repository and your render.yaml, then deploys 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.”
Render is a good platform right up until it is not.
Nothing below is a criticism of how Render works. They are the boundaries of the model: a platform that runs your services in its own account can only ever offer you what it has already built.
Five regions, and a service cannot move between them
- Oregon, Ohio, Virginia, Frankfurt and Singapore. If your customers or your regulator need somewhere else, there is no somewhere else. Render also does not support changing the region of an existing service - you create a new one and migrate the data across. And because each region has its own private network, two services in two regions cannot talk privately at all; that traffic crosses the public internet and you secure it yourself. In your own AWS account a region is a deployment parameter. Any commercial AWS region, with multi-region and multi-cluster from one control plane.
The features that make it production-grade are plan gates
- Autoscaling, preview environments and audit logs start at Pro. SAML SSO, SCIM and HIPAA-enabled workspaces start at Scale. Dedicated outbound IPs need Pro and then cost an additional monthly fee on top. Even reading Render’s SOC 2 Type 2 report requires Pro and an NDA. None of these are exotic - they are what a security review asks about, and each is a line on a pricing page rather than a property of infrastructure you control. In your own account, AWS IAM governs access, CloudTrail records what happened, and the three fixed egress IPs are simply how the network is built. No tier attached.
Fixed instance shapes, and disks that block scaling
- Instance types are fixed RAM and CPU tiers, so a service needing slightly more memory buys a whole size class more of everything. A service with a persistent disk attached cannot run more than one instance at all, which turns a storage decision into a hard scaling ceiling. On EC2 the node shape is yours to choose, storage is a volume claim rather than a constraint, and Qovery can place interruptible pools on cheaper capacity while the web tier stays on demand.
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 render.yaml Blueprint, a Dockerfile, a build command, a set of environment variables - 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 Render environment variables to Qovery variables and secrets, and shows you the plan. You approve it before a single resource is created - and your Render 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 render.yaml scheduler cron 2 jobs database PostgreSQL 15 Render Postgres, 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 Render stack keeps serving traffic untouched.
You pay AWS directly. And you can finally negotiate.
Render prices an instance tier and that is the price. AWS prices a machine and then lets you discount it - Savings Plans, Reserved Instances, Graviton and Spot are all things you can buy as the customer. There is no equivalent to buy on a Render plan, because you are not AWS’s customer. Render is.
Depends on your instance types and counts, your Postgres and Key Value plans, egress, data volume and region. A migration engineer will model your estate against the equivalent AWS shape before you commit to anything.
Three levers AWS gives you that an instance tier does not.
A Render instance type is a fixed amount of RAM and CPU at a fixed price. Once the same workload runs in an AWS account you own, the price of compute becomes something you can act on.
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. Render has no commitment tier to sell you - the instance type has one price and you pay it for as long as the service runs. 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 service.
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. Render does not expose the processor your instance runs on, so it is not a choice you currently have.
Spot capacity for the work that can be interrupted
- Background workers, cron jobs 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. On Render every instance of a given type costs the same whether it is serving payments or retrying a queue, because the platform has no way to express that difference.
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.
- Render runs all of this in its own 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 service on AWS,
live within the hour.
Any commercial AWS region - not a list of five - with multi-region and multi-cluster from one control plane. Nothing you do here touches your existing Render services 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 →Render to AWS
Something not covered here? Talk to a migration engineer - they have done this on estates larger than yours.