Off Heroku, off GCP, off Azure, off on-prem. We've done your exact migration shape before, file the AWS migration funding application ($25K–$200K), and run the cutover. Day 1 is a written assessment, not a sales call. $0 to you.
These three patterns drive most of the migration inquiries we route. The math is rarely the blocker — finding someone who has actually done it on your stack is.
You're paying 4–8x what AWS would cost at your scale. Series-A board meetings are starting to surface "infra cost as % of revenue" as a metric. You need to be off — but the team that's shipping product can't also run a cutover.
Acquired into an AWS shop. Or your AI workload needs Bedrock + Claude. Or your enterprise customers signed a BAA that's AWS-only. Whatever the reason, you're moving — and you need someone who's done it cleanly without a 6-month death march.
A $500K capex decision is on the table, the data center contract is up for renewal, and you'd rather pay opex. AWS funds the move end-to-end — $0 to you.
AWS has a migration funding pool for teams moving workloads onto AWS. Direct-to-customer self-serve, the ceiling is small. With the right application — AWS commitment data + a delivery plan AWS trusts — the same workload can unlock 5–10x more.
We file the funding application as part of the readiness phase — you don't fill out forms. AWS approves migration funding in 2–4 weeks, in parallel with your cutover plan. By the time you're ready to move, the funding is sitting against the project.
A migration is the cleanest moment to add a Bedrock + Claude prototype budget. AWS has GenAI re-platform credits (separate pool from migration funding) for teams that bake AI into the new architecture. Most teams don't know to ask. We do.
Tell us what you're building. We figure out which credit programs you qualify for and submit the applications. No technical knowledge needed.
B2B SaaS, 40 engineers, $11K/mo on Heroku Enterprise, 6-month deadline
Multi-region requirement from a new enterprise customer. Heroku can't do it. Internal team had attempted a partial AWS setup 18 months earlier and abandoned it. Procurement was about to add a $400K Heroku Enterprise renewal.
Written assessment in week 1. Containers + managed database + multi-region active-passive plan in week 2. Production cutover at week 11. AWS funded the entire engagement end-to-end — customer paid $0. Heroku Enterprise renewal cancelled.
We use this to route you to the right partner — and to flag credit eligibility before the discovery call. Form fields are kept; you're not in a CRM the moment you start typing.
For a single-region SaaS app: typical 6–12 weeks from kickoff to production cutover, depending on data volume and downtime tolerance. Multi-region or compliance-driven moves are 3–6 months. The assessment is week 1; the actual cutover is the last 2 weeks of the project.
We file the application. AWS funds the engagement end-to-end through their migration funding programs. For the workloads we take on, the engagement is fully AWS-funded — you don't get an invoice from us. You get the credits + the migration. $0 to you.
We match by stack tag. Off-Heroku to containers, off-Oracle to Postgres on AWS, off-GCP to kubernetes on AWS — we filter by what we've shipped before. If your stack isn't a fit, we tell you up front instead of taking it on wrong.
Yes — there's usually a forward-spend commitment. We size the commit during assessment so it matches what you'd organically spend post-migration. The funding number scales with your commitment — so a bigger workload move = bigger funding pool.
We can pick it up for the second half. The funding case is harder mid-migration but not impossible. Tell us where you are in the form notes; we'll tell you straight whether there's funding still on the table.
No. You're free to talk to anyone. We just won't double-handle the same inquiry — once we're engaged, we have 90-day protection on you so we can invest properly in your assessment.