Cloud readiness scorecard

Fifteen yes/no questions, based on the audit we run in the first week of every engagement. Answer honestly; you get a red, amber or green score for each area and the first thing to fix.

Security

Every person signs in through SSO, and nobody uses long-lived personal access keys.

The production database is not reachable from the internet, and secrets live in a secrets manager, not in code or .env files.

Audit logs (e.g. CloudTrail) are enabled everywhere and kept in a separate, locked-down account.

Cost control

A named person reviews the cloud bill every month and can change it.

At least 80% of spend is tagged by service or owner.

Non-production environments scale down or switch off outside working hours.

Infrastructure as code

More than 90% of production infrastructure is defined in Terraform, OpenTofu, Pulumi or CloudFormation.

Infrastructure state is stored remotely with locking, and nobody applies changes to production from a laptop.

You could rebuild a whole environment from code in under a day.

Observability and on-call

Logs from every production service land in one searchable place.

Alerts page a human on user-visible problems (errors, latency), not on CPU thresholds.

There is an on-call rotation with paging, escalation and a runbook per alert.

Resilience and recovery

A backup has been fully restored, successfully, in the last six months.

Production databases and services run across more than one availability zone.

There is a written recovery plan with target RPO and RTO, and it has been rehearsed.

0/15 answered

Frequently asked questions

What does the cloud readiness scorecard measure?

Five areas that decide whether a cloud setup is safe to grow on: security posture, cost control, infrastructure as code, observability and on-call, and resilience and recovery. Each has three yes/no checks taken from the audit rubric we use with clients.

Is my data stored?

No. The scorecard runs entirely in your browser. Nothing you click is sent to us unless you choose to contact us afterwards.

What should I do with a red result?

Fix red areas first, starting with security and recovery, because they carry the most risk. Each red area links to a guide with the concrete steps. If you want an expert to check the details, our one-week cloud audit goes through the same areas in depth.

Tell us what you need