Why this assessment exists

Multi-cloud exit readiness matters even when you don't plan to exit. Readiness is leverage at renewal, risk reduction against single-vendor outage or pricing, and a strategic option that changes in value as AWS pricing and policies evolve.

This assessment maps your exit readiness against the dimensions that distinguish truly portable estates from effectively captive ones. Built on 40+ multi-cloud readiness reviews.

Your progress 0% complete
Question 1 of 8

What percentage of production workloads are architecturally portable (containerised, IaC, no AWS-proprietary services)?

Containerised + IaC + minimal-AWS-proprietary workloads are portable. Heavy use of AWS-proprietary services creates captivity.

Question 2 of 8

What is your data-gravity exposure (S3 / RDS / DynamoDB petabytes that would need to move)?

Data-gravity is the #1 exit obstacle. Egress cost, re-platforming cost, and timeline all scale with data volume.

Question 3 of 8

Are your tooling (CI/CD, monitoring, IaC) portable across clouds?

Terraform, Kubernetes, cloud-agnostic monitoring, and CI/CD are portable. AWS-native tooling (CodeBuild, CloudWatch-only) creates captivity.

Question 4 of 8

Does your engineering team have meaningful multi-cloud capability?

Multi-cloud capability is team-level, not tool-level. Teams that have only ever worked on AWS face real learning-curve exposure.

Question 5 of 8

Does your AWS contract include explicit exit / termination rights with reasonable cure periods?

Exit clauses determine what a realistic exit window looks like and the commercial conditions that apply.

Question 6 of 8

Is your cloud governance model ready for multi-cloud (FinOps, security, identity federation)?

Multi-cloud governance is a discipline — FinOps across clouds, unified identity, unified security posture. Single-cloud governance doesn't scale.

Question 7 of 8

Do you have a credible financial exit-cost model (egress, re-platforming, parallel running)?

Exit cost must be modelled credibly to make exit decisions. Unmodelled exit cost = uncredible exit posture = no renewal leverage.

Question 8 of 8

Does executive leadership (CIO / CTO) support maintaining exit readiness as a strategic discipline?

Exit readiness requires ongoing investment. Strategic executive support distinguishes programmes that stay ready from those that drift.

0 of 8 answered

What happens next

When you click View your results, we'll ask for your name, work email, and company. We only accept corporate email addresses — no Gmail, Outlook.com, or other free providers — because this report is written for enterprise buyers and we use the domain to tailor the recommendations. Your email is never sold, shared, or used for anything other than delivering your report and (if you opt in) related AWS research.

Once you submit, you'll be redirected to a personalised report showing your overall score, risk band, the specific findings for each question where you scored 2 or higher, and the three most important actions to take before you sit down with AWS.

Prefer to walk through this with an expert?

Our AWS practice will run the full diagnostic with you in a 2-hour working session.
Book a session →