01 / MIGRATION
Link your repository
Connect GitHub, GitLab, or Bitbucket. StationOps detects your stack and proposes AWS infrastructure that matches how your Heroku app is built.
MIGRATION GUIDE
A practical path from Heroku to infrastructure in your AWS account, ready for the security and technical requirements a customer will check.
An illustrative comparison of engagement and platform patterns. Offerings vary by provider and contract; confirm the requirements and scope for your environment.
| Heroku | StationOps |
|---|---|
| Git-based deploys | Repo connect from GitHub, GitLab, or Bitbucket |
| Shared dynos | Your own Fargate tasks and ECS services |
| Managed Postgres add-on | RDS Postgres you control and can snapshot |
| Redis add-on | ElastiCache Redis or Memcached |
| Review apps | Preview environments on every plan |
| Config vars | Environment variables with dashboard and CLI |
| Add-on catalog | Run what you need — it is your AWS account |
| Private Spaces | Isolated AWS accounts and compliant landing zones |
| Request timeout limits | No platform-imposed HTTP timeout |
| Runs on Heroku hardware | Runs in your AWS account and billing |
| Hard to take infra with you | Export infrastructure as CDK anytime |
01 / MIGRATION
Connect GitHub, GitLab, or Bitbucket. StationOps detects your stack and proposes AWS infrastructure that matches how your Heroku app is built.
02 / MIGRATION
Dump Heroku Postgres, restore into RDS, and wire Redis or other services into ElastiCache. Run old and new environments side by side while you validate.
03 / MIGRATION
When you are ready, update DNS to your new endpoints. Roll back quickly if needed — your Heroku app can stay up until you cut over.
Map web, worker, and release commands to StationOps service definitions. Fargate runs each process type with the resources you configure.
Run heroku config -s, then import the output through StationOps. Secrets live in your AWS account, not on a shared platform.
Postgres, Redis, and Memcached are built-in components — no marketplace markup. Third-party APIs like email providers keep working unchanged.
Without Heroku dyno cycling, memory behaviour may look different. Watch usage in the first week and right-size Fargate tasks from real data.
Agree the application mapping, data migration, validation, cutover, and recovery approach before moving production traffic. Cost and timing depend on your workload and the services it needs.
Essential is €1,500 per month with a €10,000 deployment fee. Professional is €2,500 per month, with a deployment fee of €10,000–€20,000. Cloud usage is billed separately.
Explore managed packagesYes. Heroku has moved to sustaining engineering — maintenance and security, not new product investment. Nothing forces you off today, but there is no meaningful roadmap to bet on either.
A straightforward app often lands on AWS in a day. Larger setups with multiple services, data migration, and compliance requirements usually take a few days to a couple of weeks.
Usually very little. Dependencies, buildpacks, and twelve-factor patterns carry over. The shift is where things run — your AWS account — not a rewrite of the application.
That is the common case. StationOps provisions networking, compute, databases, TLS, and monitoring. You keep a PaaS-style workflow without hiring for AWS full time.
Yes. The managed service covers architecture, data transfer, cutover, and ongoing compliance. Essential is €1,500 per month with a €10,000 deployment fee. Professional is €2,500 per month with a deployment fee of €10,000–€20,000.
Nothing changes for external APIs. Update env vars if endpoints change after cutover. Only infrastructure that lived on Heroku add-ons moves onto AWS components you own.
Tell us what you’ve built and when you want to launch. We’ll discuss the requirements and whether we can help.