Skip to main content
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.
CloudEval is Azure-first today, with additional cloud providers coming. For the fastest first result, start with a single ARM template or Bicep-generated ARM JSON. For linked templates, use an IaC workspace with .cloudeval/config.yaml.

​
What you can do today

  • Connect Azure with Cloud sync and sync its resources into a project.
  • Import a single ARM/Bicep-generated template before deployment.
  • Import multi-file ARM workspaces with nested or linked templates.
  • 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.
  • Sync GitHub repositories through the CloudEval GitHub App for branch-based IaC projects (GitHub repository sync).
  • Use the GitHub Action for CI jobs on GitHub with access keys, merge gates, PR comments, and report artifacts (GitHub Actions integration).
  • Use CLI completion for faster command discovery in Bash, Zsh, Fish, and PowerShell.
  • Use llms.txt and llms-full.txt when you need machine-readable product and CLI context.
CloudEval workspace showing project files and reports

​
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 Cloud sync projects and IaC changes before rollout.

​
The product model

CloudEval is built around four ideas:
  1. Connection: how CloudEval reads either Cloud sync, a single IaC template, or a multi-file IaC workspace.
  2. Project: the working space where topology, files, reports, and sharing come together.
  3. Reports: the outputs that turn a project into cost and architecture findings.
  4. Sharing: the controls for publishing a read-only view or collaborating with named teammates.

​
Start here

Sync GitHub repo

Install the GitHub App, import a branch, and keep IaC projects refreshed from GitHub.

Connect Azure

Cloud sync for a current-state view of a subscription or resource group scope.

Import IaC

Single templates, parameters files, and nested ARM workspaces.

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.

​
Next step

Open How CloudEval works to learn the platform model, or jump straight to the quickstart if you want hands-on setup.
Last modified on June 5, 2026