What gets automated
Cloudeval automates the repeatable parts of review: gathering supported project context, generating report outputs, attaching evidence, and making findings inspectable in the product and automation surfaces.
Solutions
Last reviewed 2026-09-30
Automated Well-Architected review for Azure teams
Overview
Cloudeval helps automate Azure Well-Architected-style review by turning supported Azure and ARM/Bicep project context into architecture findings, pillar-oriented reports, evidence-backed explanations, and repeatable review workflows across the web app, CLI, GitHub Actions, and MCP-compatible agents.
What still needs human review
Findings remain evaluations and recommendations, not compliance attestations. Teams should review business context, production constraints, and accepted risk before making changes.
Where this fits in delivery
The workflow fits before merge, before production rollout, during cloud posture review, and when a stakeholder needs a shareable report rather than raw infrastructure data.
Pillar review without overclaiming
Use the five pillars to organize questions about reliability, security, cost, operational excellence, and performance efficiency. Treat each result as an evaluation of the supplied scope and checks that ran, not as a certification.
- Start with ARM JSON, Bicep compiled to ARM JSON, or a documented Azure sync.
- Keep skipped checks, missing inputs, and stale observations visible in the decision.
- Use configured CI thresholds for repeatability, then have an owner review exceptions.
FAQ
Does Cloudeval replace the Well-Architected Framework?
No. It helps operationalize architecture review signals and evidence, but the framework and final review judgment still belong to the team.
Are the findings compliance attestations?
No. Public docs describe them as evaluations and recommendations, not compliance attestations.
