Cloud Assurance

Continuous architecture review against the Well-Architected pillars, instead of a slide deck once a year.

Runs today, on Google Cloud

Connect a Google Cloud project and this module reads it. Today that means:

Cloud SQL backup configuration and durability settings
Cloud Storage bucket versioning
Log sink retention and export
Whether any alerting policy or uptime check exists at all

It reads Google Cloud only, not AWS or Azure, and it does not track remediation. Everything further down this page is where the module is going, not what it does now. The wider review is work we do as an engagement — AWS Well-Architected Review.

THE PROBLEM

Why this module exists

A Well-Architected review is a snapshot. The estate keeps moving after it — new accounts, new workloads, quiet drift — and by the time the next review lands, the report describes a system that no longer exists.

INTENDED SIGNALS

What it is being built to surface

Descriptions of intent. No findings exist yet, because nothing is connected yet.

Architecture drift

Where the running estate has diverged from the design that was signed off.

Pillar coverage

Which of the six pillars have been genuinely assessed for a workload, and which were skipped.

Risk, ranked by exposure

Findings ordered by what is actually reachable and what it would cost, not by a severity label alone.

Remediation state

What was raised, what was fixed, and what quietly stayed open.

SCOPE

What the module covers

Workload and architecture assessment
Security, reliability, performance, cost, operational excellence, sustainability
Risk prioritisation and remediation tracking
Audit-ready reporting

Tell us what this would need to catch

We are designing this against real environments. If this is a problem you have, the fastest way to shape it is a conversation with the engineers building it.

Talk to an Engineer