| What it is | Tools, funding and partner programs for moving workloads into one provider’s cloud | A system of record for how your software works that plans, performs and verifies change |
| Built for | Rehosting servers and VMware estates, moving databases and converting selected code | Changing applications, databases and jobs, including the changes a move depends on |
| Destination | The provider’s own platform | The cloud and database you choose |
| What it maps | Servers, network flows and databases, with separate code tools per platform | Code, stored procedures, pipelines, configuration and infrastructure definitions in one graph |
| Planning | Wave plans, landing zones and business cases | A step-by-step plan from one sentence, with target files and an estimated cost |
| Who does the work | Your team, with the provider’s experts and funded partners | Your team, with Aedeon’s agents under their approval; services partners are optional |
| How the result is checked | From compile checks to generated equivalence tests; production replay for mainframe moves to Google Cloud | Production traffic replayed against the old system; a divergence stops the gate |
| How it is paid for | Tools often free; credits and partner funding tied to new spend in that cloud | Published plan prices plus credits; every change priced before approval |
| Where it runs | A managed service in the provider’s cloud, with collectors in your data center | A private VPC in your cloud; your own cloud on Max; sovereign region or air-gapped on Virtual Private Aedeon |
| What you keep | The workload, running in the new cloud | A changed system, a graph that keeps updating, and every change in your Git |
| Best fit | Infrastructure moves to a cloud you have already chosen | Application changes that must be proven before cutover, on any destination |