Usecase · Migrate from Heroku

Migrate from Heroku to your own AWS cloud without any DevOps effort.

Outgrowing Heroku? Build and deploy without limits on your cloud account.

Heroku logoAWS logoAWSGCP logoGCPAzure logoAzure

No credit card required

Why migrate

Why move to your own AWS, GCP or Azure account.

  • 3–4× lower hosting bills

    Heroku's dyno + add-on pricing grows fast at production scale. Your own cloud bill spikes in week one, then plateaus.

  • 100+ regions

    Run anywhere AWS, GCP or Azure go — including sovereign and edge regions Heroku doesn't reach.

  • 896 vCPU & 32 TB RAM

    Scale a single workload to any size — no Performance-L dyno ceiling, no per-app limits.

  • More control

    Your VPC, your IAM, your KMS, your audit trails. Nothing hidden behind someone else's abstraction.

Cloud setup

Migrate in under a week, we handle the move.

No DevOps skills required. No need to learn AWS, GCP or Azure primitives. Connect a cloud account and a git repo — LocalOps wires up the rest in under 30 minutes.

See how it works in our docs

BeforeDays of plumbing

Wrestle with AWS / GCP / Azure configuration

VPCs, subnets, IAM, TLS, databases — every new service drags this list along behind it.

  • VPC + subnets
  • NAT gateways
  • EC2 + ASGs
  • Security groups
  • IAM roles
  • Nginx config
  • SSL certs
  • RDS + backups
AfterMinutes on the console

Deal with similar primitives you used in Heroku

LocalOps owns everything underneath. You think in environments and the services inside them — same shape as Heroku's apps and dynos.

  • Environments
  • Services
Service types
  • Web
  • Internal
  • Worker
  • Job
  • Cron
CI / CD

LocalOps + your cloud = same git-push developer experience. No DevOps effort.

Every service ships with CI/CD against your cloud, out of the box. Devs push, LocalOps deploys with zero downtime.

  1. git push

    developer

  2. webhook

    LocalOps receives

  3. pull + build

    image built

  4. deploy

    zero-downtime

Pull requests

Test changes with the same experience, for every pull request.

Open a PR — preview it on a unique URL, isolated from production. LocalOps spins up an ephemeral copy of your service and tears it down on merge.

  • Isolated, ephemeral copy of the service per PR
  • Your team tests on a unique preview URL
  • Merging the PR cleans up the environment
pr-42.orders-api.localops.run
#42 · Add Stripe webhook retry
alice → main
preview ready
  • Branch
    fix/stripe-retry
  • Built
    1m 42s ago
  • Deploy time
    00:38
Merging this PR will tear down the preview environment.
Monitoring

Pre-built monitoring suite, no extra add-on to buy.

Loki, Prometheus and Grafana come wired up with every environment — for your infrastructure and your code.

See monitoring in our docs

  • Logs
  • Metrics
  • Alerts
  • Infrastructure
  • Your code
Scaling

Same auto-scaling, just cheaper to run.

Handle a launch-day spike without re-architecting. Scale proportional to CPU or memory on your own cloud — or pin a service to a fixed instance count when you want explicit control.

  • Auto-scale proportional to CPU or memory
  • Min / max replica count per service
  • Manual scaling on demand from the console
Cost comparison · Heroku vs your cloudover time
  • Heroku
  • AWS / GCP / Azure on LocalOps

Heroku's cost curve climbs with dyno hours and add-on tiers. Your cloud bill climbs in the first few weeks, then quickly plateaus.

Built-in

Everything you'd expect, built-in, and more.

  • Private networking from day one

    Services live inside your VPC by default — internal traffic stays off the public internet.

  • Encrypted secrets

    Per-service secret store with versioning and audit, encrypted at rest in your cloud's KMS.

  • Role-based access for cloud resources

    Scoped IAM roles per service — no broad keys handed around.

  • Encrypted volumes

    Every persistent disk LocalOps provisions for your services is encrypted by default.

  • Auto-renewing SSL certs

    Free, auto-renewing TLS certificates for every public service. No cron jobs.

  • SOC 2-ready, from day one

    Hardened cloud configuration, audit trails and continuous compliance evidence from launch.

Above all — fantastic support and guidance from our DevOps team, right in your Slack or MS Teams channel.

4 steps · 30 mins

How to get started in 30 mins.

  1. Connect your cloud account

    AWS logoAWSGCP logoGCPAzure logoAzure
  2. Connect your git repo

  3. Create an environment

    VPC, Kubernetes, observability — wired up on your cloud in 15–20 minutes.

  4. Deploy services

    Go live on yourapp.localops.run or your domain

Migrate now

Let us be your DevOps partner during the migration, and after.

No DevOps skills required. Our team plans the move, runs it alongside your engineers, and stays in your Slack channel after cutover.

FAQs

Questions Heroku users usually ask.

Can't find what you're looking for? Email support@localops.co.

How long does a Heroku → AWS / GCP / Azure migration actually take?

The platform is ready in under 30 minutes once you connect a cloud account and your repo. Migrating the workload itself — services, data, DNS, cutover — typically takes under a week for a single-app setup, and our team runs it with you.

How much can I expect to save?

Most teams cut hosting bills 3–4× over 12 months. Heroku's dyno + add-on pricing grows with every Performance dyno and Postgres tier; your own cloud bill plateaus once you're on right-sized compute with reserved or savings-plan pricing.

Do I need to write Dockerfiles, Helm charts or YAML?

No. LocalOps detects your stack (Ruby/Rails, Node, Python, Go, etc.) and builds container images for you. Bring your own Dockerfile if you want, but it's not required.

What happens to my Heroku Postgres / Redis?

We provision equivalents on RDS / Cloud SQL / Azure Database and ElastiCache / Memorystore in your own cloud, run a one-shot data migration with our team, and cut DNS over once it's caught up.

Will I lose review apps?

No. Every PR can get its own ephemeral environment on your cloud — same DX as Heroku review apps, but on your VPC.

Can I keep my AWS / GCP / Azure credits?

Yes — that's the point. Cloud compute, storage and network stay on your cloud bill at standard pricing. LocalOps only charges for the platform subscription.

What about Heroku add-ons like Papertrail or Scheduler?

Logs and metrics are covered by the built-in Loki + Prometheus + Grafana suite. Scheduled jobs run as cron services natively. Most other add-ons map to a cloud equivalent we'll set up during migration.

Do I need a DevOps engineer on staff?

No. Pro and Business plans include chat / Slack support staffed by real DevOps engineers, and there's a fully-managed engagement for teams without any DevOps bandwidth.

Is there a free plan?

Yes — Starter is free for teams up to 3 users with 2 cloud accounts and 2 environments. No credit card.