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.

Running reports is only the middle of the job. The real value comes from how the team reviews what CloudEval found.
CloudEval priority decisions list showing findings, affected resources, and review recommendations
  1. Start with architecture critical issues.
  2. Move to architecture high-severity issues.
  3. Review the top cost opportunities.
  4. Decide which findings need immediate action, follow-up, or simple documentation.

​
What to pull out of the architecture report

  • overall score
  • weakest pillars
  • critical issue count
  • high issue count
That gives you a fast picture of severity before the team gets lost in detail.

​
What to pull out of the cost report

  • current monthly and annual context
  • biggest service families
  • top savings opportunities
Use cost findings to drive a narrower next step list, not just a large spreadsheet-style discussion.
CloudEval report drilldown showing issue counts, cost context, security score, architecture score, top actions, and breakdown chart

​
Good review questions

  • What is genuinely urgent?
  • Which issue is high-confidence and easy to fix?
  • Which finding should block rollout?
  • Which items can be tracked for later instead of being solved immediately?

​
Next step

If the project is ready for broader review, continue to Share results with stakeholders.
Last modified on May 5, 2026