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
Move from Heroku. Keep moving forward.
A practical path from Heroku to infrastructure in your AWS account, with platform automation and managed engineering support when you need it.
Plan around the differences.
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 |
A deliberate migration path.
02 / MIGRATION
Bring your data across
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
Point traffic at AWS
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.
Process types and Procfiles
Map web, worker, and release commands to StationOps service definitions. Fargate runs each process type with the resources you configure.
Config and secrets
Run heroku config -s, then import the output through StationOps. Secrets live in your AWS account, not on a shared platform.
Replacing add-ons
Postgres, Redis, and Memcached are built-in components — no marketplace markup. Third-party APIs like email providers keep working unchanged.
After the move
Without Heroku dyno cycling, memory behaviour may look different. Watch usage in the first week and right-size Fargate tasks from real data.
Move with a clear
operating plan.
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.
Managed service pricing starts at $1,497 per month, with one-time implementation fees and cloud usage billed separately.
Explore managed packagesQuestions worth asking.
01Does Heroku still work for existing apps?+
Yes. 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.
02How quickly can we move?+
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.
03How much app code needs to change?+
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.
04We are a small team without dedicated DevOps — is that OK?+
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.
05What happens to SendGrid, Stripe, and other SaaS integrations?+
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.
THE NEXT ADVANTAGE IS YOURS
Make CloudOps an
advantage for your business.
Your cloud. Our responsibility.
Talk to a Cloud Expert