If the answer is the review gate, your guardrails are not holding. In 2 to 3 weeks we assess your landing zone against the Well-Architected framework, with evidence from the estate. You leave with a backlog someone can fix.
Teams route around controls. Findings pile up before every audit. A release waits days for a review that checks the same things each time. The landing zone was built before the current team arrived, and nobody has assessed it since.
Guardrails applied as gates, not as modules. A control that needs a request gets bypassed. A module a team can use on its own gets adopted.
Compliant by default, with no review step.
Days per release lost to review gates. Audit findings still open. The assessment turns them into a gap you can price.
At mid-size enterprises on Azure or AWS, with a landing zone nobody has assessed since it was built.
Who need an independent, senior assessment of a client's platform, delivered under their name or ours.
Organisations working through an MSP, where audit evidence has to come from the estate.
With Kubernetes in scope: AKS, EKS or GKE.
Every finding points at a resource someone can fix.
Read access to the estate. We pull Resource Graph on Azure or Config on AWS, with Traffic Analytics or flow logs. We read policy state, identity and access, the pipelines, and the Terraform or Bicep that built it. One interview per owning team, after we have read the estate.
Findings against the pillars of the Well-Architected framework and against the landing-zone design. That covers identity, network topology, policy and governance as code, pipelines, the monitoring baseline, and Kubernetes defaults when AKS, EKS or GKE is in scope. Each finding is tied to a resource, a policy or a pipeline.
A prioritised remediation backlog with owners, in your backlog tool. A read-out with the people who will fix it. A proposal for what follows, or a note that says nothing needs to.
From 9,000 euros, excluding VAT. The indicative band is 9,000 to 14,000 euros, depending on the number of subscriptions or accounts and whether Kubernetes clusters are in scope. The price is fixed in the proposal before we start.
For a Dutch municipality, through our MSP partner Infield ICT, we assessed an AKS landing zone built on Bicep and Azure DevOps against the Well-Architected framework. Resource Graph and Traffic Analytics were the evidence, so every finding pointed at a resource someone could fix. The in-house team then ran the platform itself after a nine-session enablement programme. At Liberty Global and Virgin Media we defined the guardrails for AWS, Azure and GCP and shipped them as self-service Terraform modules and pipeline templates. A team that used the modules was compliant by default, and nobody waited for a review.
Good. Our public-sector and healthcare work arrives through MSP partners. We deliver under their name or ours, and the backlog goes to whoever fixes it.
No. The proposal names the follow-on and its trigger. If the evidence says nothing follows, we say so.
Read access to the estate, one owner per team for a 45-minute interview, and the two numbers above.