Deploy & Migration
Repository-to-cloud deployment planning — analyse a repo, compare deployment paths across clouds, generate infrastructure blueprints, and run the migration.
At a glance
| Route | /deploy-migration |
| Group | Analyze |
| Page permission | intelligence |
What it is
Repository-to-cloud deployment planning. It analyses a GitHub repository, compares deployment paths across clouds, generates AWS-ready infrastructure blueprints, and runs the migration control plane that executes and tracks the move.
Who it is for
Platform engineers and architects planning a migration or a new deployment, and the finance stakeholders who need it costed first.
How it works
The module reads a repository and infers what it needs to run — runtime, dependencies, data services, network requirements. It then compares deployment paths across AWS, Azure, GCP, Oracle, and hybrid options, costing each.
From the chosen path it generates a deployment blueprint expressed as Terraform or OpenTofu, which can be planned, reported on, and then executed as a tracked run with a full event stream.
Discovery services per provider inspect what already exists, so a migration plan accounts for current state.
Features
- GitHub repository analysis with branch selection
- Cross-cloud deployment path comparison across AWS, Azure, GCP, Oracle, and hybrid
- AWS-ready blueprint generation in Terraform and OpenTofu
- Blueprint editing and plan generation
- Per-blueprint deployment report
- Migration run execution with a per-run event stream
- Per-provider deployment discovery of existing infrastructure
- Readiness assessment before any run
- Cost planning integrated into the path comparison
How to use it
Connect GitHub and confirm readiness
In Integrations, then check the readiness panel here.
Review the inferred requirements
Against your team's understanding of the application. Inference is good, not infallible.
Compare deployment paths
Weighing cost against the operational characteristics of each. Cheapest is not always right.
Generate a blueprint and review the generated code
Read the generated infrastructure code before doing anything with it. It is real Terraform that will create real resources.
Run a plan and read the report
This is the point at which cost and resource implications become concrete.
Validate resulting cost against the plan
In Overview and Cost Center once the deployment is live.
Why it matters
Migration and greenfield deployment decisions commit an organisation to a cost structure for years — yet are usually made without a costed comparison, because producing one manually is prohibitively slow.
Automating repository analysis, path comparison, and blueprint generation makes the costed comparison the default rather than the exception.
And generating real infrastructure code means the plan and the deployment cannot drift apart.
Connects to
- Shares GitHub integration with PR Cost Review and CI/CD Control Tower
- Pricing shared with Cloud Playground
- Resulting infrastructure appears in Inventory