CloudEval AI turns cloud environments and infrastructure-as-code into a shared evaluation workspace for cost, architecture, reliability, and review. Use it to catch expensive, fragile, or hard-to-explain infrastructure decisions before they reach production, then share the evidence with the people who need to act.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.
What you can do today
- Connect Azure and sync its resources into a project.
- Import ARM or Bicep templates before deployment.
- Run cost and architecture reports from the same project.
- Review Well-Architected scores, issue counts, and optimization opportunities.
- Share a read-only project view or invite collaborators.
- Use the CLI for scripted imports, report runs, grounded questions, and app deeplinks.
- Use CLI completion for faster command discovery in Bash, Zsh, Fish, and PowerShell.
- Use
llms.txtandllms-full.txtwhen you need machine-readable product and CLI context.

Why teams use it
- Executives use it to get a faster read on cost exposure, risk, and project health.
- Cloud engineers and architects use it to inspect topology, review reports, and prioritize fixes.
- DevOps and platform teams use it to evaluate live Azure environments and IaC changes before rollout.
The product model
CloudEval is built around four ideas:- Connection: how CloudEval reads either a live environment or an IaC source.
- Project: the working space where topology, files, reports, and sharing come together.
- Reports: the outputs that turn a project into cost and architecture findings.
- Sharing: the controls for publishing a read-only view or collaborating with named teammates.
Start here
Start with GitHub
Fastest browser path from a template URL to a project, diagram, and report.
Connect Azure
Best path when you need a current-state view of a live subscription or resource group scope.
CLI, agents, and MCP
Best path for JSON output, scripting, local agent workflows, and MCP-compatible tools.
What these docs optimize for
- Fast onboarding to a real result, not a tour of every screen.
- Honest feature coverage, especially around provider support.
- Task-based guidance you can use during evaluation, review, and sharing.
- Reference pages that match the product as it exists today instead of a generic cloud-AI story.
- Agent-readable context for CLI, MCP, and automation workflows.
