Skip to main content

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.

Once you have a project, reports are the fastest way to turn CloudEval into something actionable.
CloudEval reports overview with posture score, critical issue count, run-rate cost, savings, priority decisions, and freshness context

Run a report

  1. Open Reports.
  2. Choose Add report or the equivalent report action from the project flow.
  3. Select one or more projects.
  4. Choose the report types you want:
    • Cost
    • Architecture
    • Both
  5. For cost runs, confirm the region and currency.
  6. Start the run.

What you should expect

  • Cost output with monthly and annual context, breakdowns, and opportunity summaries
  • Architecture output with overall score, pillar scores, and issue counts
  • Latest report snapshots attached to the project for later sharing or review

Which report should you start with?

  • Start with both if you are new to the product.
  • Start with cost if the immediate question is spend or optimization.
  • Start with architecture if the immediate question is quality, risk, or review readiness.

What to do after the first run

  1. Review the highest-severity architecture issues first.
  2. Review the top cost opportunities next.
  3. Decide whether the findings should stay private, be shared internally, or be published as a read-only share.
CloudEval prioritized issue list showing architecture findings, severity, affected resources, and recommendation summaries

Next step

Read Reports for the mental model, or use Review cost and architecture findings for a practical follow-up workflow.
Last modified on May 5, 2026