This page is the shortest stable description of how CloudEval is structured.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.
Core objects
| Object | What it represents | Why it matters |
|---|---|---|
| Connection | A source of live cloud data or infrastructure code | It tells CloudEval what to analyze |
| Project | The main working unit | It holds files, topology, status, reports, and sharing |
| Report | A generated evaluation output | It surfaces cost or architecture findings |
| Sharing state | Visibility and access configuration | It controls who can see or collaborate on a project |
Connection types
CloudEval uses two connection types:synctemplate
Project types and status
Projects can track status for:- sync
- architecture
- cost
- unit tests
Share views
CloudEval share links support these read-only view modes:previewcodesplit
Collaboration roles
Projects support:- owner
- editor
- viewer