Free cloud health check
A monthly read-only review of security, reliability and cost, checked by AI against a published checklist. Free.
Secure · Runs automatically in your portal
The problem
You do not know if your cloud is exposed, fragile or overpriced, and you have no one to ask.
What you get
- A 0 to 100 health score with trend
- Top findings in plain English with the exact fix
- Idle and oversized resources
- A report that passed its quality checklist
Deliverables
- Monthly health report (PDF and portal)
- Findings with remediation
- Score trend
How it runs
- 1Grant access
One script gives our scanner a read-only role.
- 2Scan
Hundreds of checks against CIS Benchmarks.
- 3Analyze
AI explains impact and fixes; secrets and personal data are removed first.
- 4Review
An independent AI review checks the report against its checklist before release.
The quality bar for this service
Every free cloud health check deliverable is reviewed against this checklist (version 1.0) before it is released. Items marked required must be fully met; an item that is not is flagged on the report.
- Every finding names the exact affected resource (project, bucket, rule, account or image), not a resource type.Required
- Every remediation is specific to that resource, executable as written (console steps, CLI or Terraform) and does not risk an outage without saying so.Required
- Business impact is stated in plain English from the evidence only; no claim that an attack or breach happened, no invented numbers.Required
- Severity is consistent with the scanner evidence and CIS Benchmark guidance; nothing is inflated or downplayed.Required
- The executive summary states the score and names the three most important actions in priority order.Required
- The score, the severity counts and the findings list agree with each other.Required
- Security findings carry framework references (CIS control ids) when the scanner provides them.
- The report contains no credentials, tokens, private keys or personal data beyond business contact names.Required
- Language suits a non-technical owner; jargon is explained once or avoided.
- Findings the customer accepted as risks are identified as such with their justification.