CloudEval AI is easiest to understand as an evaluation flow: add a source, create a project, run reports, then share the result with the right audience.
The core loop
- Add a connection.
A connection tells CloudEval where to read cloud data or infrastructure code from.
- Create a project.
A project becomes the working space for files, topology, report history, and sharing.
- Run reports.
Cost and architecture reports turn raw infrastructure into findings you can act on.
- Share or collaborate.
Invite teammates, publish a read-only view, or embed the result elsewhere.
Connection setup paths
CloudEval currently supports three practical starting points:
- Cloud sync: connect deployed Azure resources with a least-privilege service principal.
- Infrastructure as code, single template: upload or reference one ARM template and an optional parameters file.
- Infrastructure as code, workspace: import multiple ARM files, choose a visualization source in
.cloudeval/config.yaml, and let CloudEval resolve linked templates for diagrams and reports.
Why projects matter
Projects are the main unit of work in the product. They are where CloudEval stores:
- linked connections
- synced or imported infrastructure data
- report outputs and latest snapshots
- share settings and collaborator access
That matters because most actions in the app happen at the project level, not at the raw connection level.
What reports add
Reports are where CloudEval starts paying for itself.
- Cost reports surface spend estimates, opportunity summaries, and trend-oriented context.
- Architecture reports summarize overall quality, Well-Architected pillar scores, and high-severity issues.
The goal is not just to visualize infrastructure. The goal is to make the next decision easier.
Sharing model
CloudEval supports three broad ways to work with others:
- Private: only people with project access can open it.
- Restricted collaboration: invite named users with editor or viewer access.
- Share links: publish a read-only link or embed view when the project is appropriate to share.
What not to assume
- A provider name in the app is not the same as full support.
- A visible UI option is not always a production-ready path.
- Share links are read-only, not an editing mode.
Next step
Use the quickstart if you want to set up CloudEval now, or read Connections and Projects if you want the model in more detail. Last modified on June 22, 2026
