← All tools

Cloud maturity assessment

Review infrastructure as code, delivery, security, reliability and operations. Identify your strengths and next steps for your platform.

We do not send or store your answers. Everything runs in your browser; no email or AWS credentials required.

Answer based on your current setup. Choose “Unknown / to validate” when you lack evidence; use “Not applicable” only when a practice does not apply to your environment.

0/10 questions answered

1. Is applicable infrastructure defined as code and version controlled?

Consider the resources you manage and whether their configuration can be reviewed and reproduced.

2. Do deployments use CI/CD with checks and a tested rollback?

Applies to systems you deploy; an untested instruction does not demonstrate rollback capability.

3. Do access controls use least privilege and MFA for applicable human users?

Review administrative access, shared accounts and permission reviews; do not share credentials here.

4. Do critical data have backups with tested restores?

Consider recovery objectives and recent restore evidence, not only whether backups are generated.

5. Do critical services have observability and actionable alerts with an owner?

Include metrics, logs and evidence that alerts reach someone able to act.

6. Do services have owners and current operational documentation?

Look for an inventory, dependencies and procedures accessible to the people operating the service.

7. Are cloud costs reviewed with budgets and accountable owners?

Applies to environments with cloud spend; look for reviews and alerts, not savings estimates.

8. Are environment differences documented and configuration drift checked?

Compare relevant configurations without assuming development and production must be identical.

9. Are relevant changes reviewed and tested before production?

Consider peer review, tests and traceability proportionate to the risk of a change.

10. Is incident response rehearsed and are agreed improvements tracked?

If no incidents occurred, a controlled exercise can also provide evidence.

How scoring works

Each applicable practice has equal weight: yes = 2, partially = 1 and no = 0. Unknown = 0 conservatively: it indicates missing evidence, not an absent practice or unnecessary spend. Not applicable is excluded from the calculation. The score is the percentage of available points earned; 80 or above indicates established practices, 50 or above developing practices and below 50 an initial stage. Answer every question to receive a result; no applicable practices means no score. Always review priority actions, even with a high score.

This indicative self-assessment relies on your answers: it is not an audit, a security certification or a savings guarantee. A high score does not establish that critical risks are resolved; unknown answers require validation.