Skip to main content
Projects are where CloudEval turns source infrastructure into something a team can actually work with.

​
What a project contains

A project can contain:
  • one or more linked connections
  • synced cloud data or imported IaC files
  • report history and latest report snapshots
  • share settings
  • collaborator roles
  • project-level status for sync, cost, architecture, and related tasks

​
Why the product is project-centric

If CloudEval only stored raw connections, teams would still need another place to review findings and coordinate decisions. The project gives you a single object you can inspect, rerun, share, and fork.

​
Project types

CloudEval distinguishes between:
  • sync projects, which are built from Cloud sync connections
  • template projects, which are built from single-template or multi-file infrastructure-as-code inputs
Both end up with the same goal: a workspace where files, topology, and reports stay tied together.
Project workspace showing files, latest reports, and source structure

A project ties source files, latest reports, and workspace state to one review context.

​
Project status

Projects track operational status across the main evaluation steps:
  • sync
  • architecture
  • cost
  • unit tests
That status layer is important because it tells you whether a project is ready for review or needs another run.

​
Next step

Read Reports to understand the outputs attached to projects, or Sharing and collaboration to see how teams publish results.
Last modified on May 22, 2026