Documentation Index
Fetch the complete documentation index at: https://docs.cloudeval.ai/llms.txt
Use this file to discover all available pages before exploring further.
CloudEval turns Azure projects and infrastructure-as-code into evaluation signals across architecture, security, cost, reliability, deployment readiness, and graph topology.
Use this page when you need public-safe wording for a homepage, sales page, docs page, or stakeholder summary.
Why it matters
Evaluation counts should be clear without exposing implementation details. A user should understand what CloudEval checks, which pillars are covered, and where the numbers come from.
The safest public claim is:
CloudEval runs 650+ cloud evaluation signals across Azure architecture, security, reliability, cost, IaC readiness, diagram quality, and graph topology.
For broader product-quality copy, use:
CloudEval is backed by 1,450+ validation checks and release quality gates across cloud evaluations, reports, agents, APIs, and static analysis.
Quick example
Use this homepage metric label:
Use this supporting sentence:
Every supported Azure project is evaluated with hundreds of architecture checks, deployment-readiness tests, cost signals, and graph-based insights before findings reach the report surface.
Coverage grid
| Public category | Count | What it covers |
|---|
| Azure architecture checks | 517 checks | Security, reliability, operational excellence, performance efficiency, and cost optimization. |
| IaC deployment readiness tests | 53 tests | ARM template structure, parameters, UI definitions, and file-level readiness. |
| Architecture graph intelligence | 6 lenses, 7 scores, 3 rollups | Blast radius, critical paths, exposure, risk, cost sensitivity, and change impact. |
| Cost intelligence signals | 49 mapped Azure resource/service categories, 6 coverage signals, 2 current recommendation families | Pricing coverage, monthly and annual estimates, service-family rollups, unmatched-resource warnings, VM right-sizing, and storage-tier opportunities. |
| Diagram integrity checks | About 7 gates | Diagram syntax, node and edge shape, subgraph balance, labels, targets, and parser readiness. |
| Product release quality gates | 831 collected automated tests, 10 lint rule families | API, agent, report, billing, graph, pricing, streaming, and implementation-quality regression coverage. |
Architecture pillars
The Azure architecture checks map to the five Well-Architected pillars.
| Pillar | Checks |
|---|
| Security | 232 |
| Operational Excellence | 147 |
| Reliability | 101 |
| Cost Optimization | 19 |
| Performance Efficiency | 18 |
Public naming
Use these labels in public product copy.
| Label | Use it for |
|---|
| Azure architecture checks | Well-Architected style checks across security, reliability, operations, performance, and cost optimization. |
| IaC deployment readiness tests | Template, parameter, UI definition, and file-level readiness checks. |
| Architecture graph intelligence | Blast radius, critical paths, exposure, risk, cost sensitivity, and change-impact context. |
| Cost intelligence signals | Pricing coverage, service-family rollups, unmatched-resource warnings, and savings opportunities. |
| Diagram integrity checks | Syntax, node, edge, label, target, and parser-readiness gates for generated diagrams. |
| Release quality gates | Product QA checks for APIs, reports, agents, billing, streaming, graph, pricing, and implementation quality. |
Step-by-step use
- Use 650+ cloud evaluation signals when the sentence is about what CloudEval evaluates for a supported Azure or ARM/Bicep project.
- Use 1,450+ validation checks and release quality gates when the sentence includes CloudEval’s broader product safety net.
- Pair the number with the covered outcomes: architecture, security, reliability, cost, deployment readiness, diagram integrity, and graph topology.
- Avoid implying that graph rows, pricing catalog entries, or engineering tests are the same as compliance rules.
Common mistakes
- Do not call the 650+ number “compliance tests.” These are evaluation signals and quality checks, not a compliance attestation.
- Do not market graph topology rows as named tests. Graph analysis is deterministic scoring and traversal.
- Do not say every cost opportunity is guaranteed. Cost output depends on resource type, region, SKU, and pricing coverage.
- Do not expose internal package names in homepage copy.
Related pages
