Skip to main content
This page is the shortest stable description of how CloudEval is structured.

​
Core objects

​
Object relationship

A connection is the source CloudEval reads from. It can represent live Azure resources through Cloud sync or infrastructure-as-code content through template-backed imports.
A project is the working unit that ties source data, files, topology, report history, status, and sharing together. Most automation commands and app workflows target a project.
A report is a generated output attached to a project. Current public docs focus on cost and architecture reports because those are the main review surfaces.
Sharing state controls whether a result stays private, is visible to invited collaborators, or is exposed through a read-only share link.

​
Connection types and setup paths

CloudEval stores two internal connection categories:
  • sync
  • template
Users see three setup paths: This distinction matters for automation. A multi-file IaC workspace is not a new live cloud connection type; it is a richer template-backed source that resolves to the same diagram and report pipeline.

​
Project types and status

Projects can track status for:
  • sync
  • architecture
  • cost
  • unit tests
A project can also expose latest report metadata and dashboard summaries for cost and architecture.

​
Share views

CloudEval share links support these read-only view modes:
  • preview
  • code
  • split

​
Collaboration roles

Projects support:
  • owner
  • editor
  • viewer

​
Next step

Use Report types and statuses if you need more detail on output structure, or Share links if you are documenting access behavior.
Last modified on June 30, 2026