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.

Use this page when you need a quick, honest map of what CloudEval can do today and where the product is headed next.
Roadmap items are not shipped behavior. Treat anything marked In progress or Planned as directional until the docs or cloudeval capabilities --format json say it is current.

​
Why it matters

Cloud evaluation tools are only useful when teams know what they can trust. This map separates current product capability from roadmap direction so architects, DevOps teams, and AI agents can plan without guessing.

​
Quick check

For automation, check the live CLI contract first: 
cloudeval capabilities --format json
cloudeval mcp status --format json
cloudeval doctor --format json
Expected result: 
{
  "ok": true,
  "command": "capabilities",
  "data": {
    "commands": [],
    "domains": {},
    "mcp": {}
  }
}
The real output includes the current command list, frontend deeplinks, MCP toolsets, resources, and prompts.

​
Status labels

StatusMeaning
CurrentAvailable in the product or CLI today and safe to document as a supported workflow.
In progressActive roadmap work, not generally available yet. Use it for planning, not production commitments.
PlannedDirectional roadmap item. Scope and dates can change.
LimitedPartial, preview, disabled, or not broad enough to treat as a standard workflow.

​
Capabilities

AreaCapabilityStatusWhat users getStart here
Cloud ingestionAzure live environment connectionsCurrentConnect an Azure subscription or resource group scope and turn it into a CloudEval project.Connect Azure
IaC ingestionARM template importCurrentUpload or reference ARM JSON before deployment and evaluate it as a project.Import ARM or Bicep
IaC ingestionBicep review through compiled ARM JSONCurrentCompile Bicep to ARM JSON, then use the same import and report workflow.Automate with the CLI
Project modelProjects, connections, files, and sharingCurrentKeep topology, source inputs, reports, collaboration, and share links together.Projects
DiagramsInteractive architecture and dependency diagramsCurrentInspect cloud resources, relationships, layout, and resource context visually.Diagrams and workspace views
ReportsCost reportsCurrentEstimate cost exposure, savings opportunities, and cost review inputs.Run reports
ReportsArchitecture and Well-Architected reportsCurrentReview pillar scores, findings, issue counts, and architecture recommendations.Report types
ReportsSecurity and architecture finding reviewCurrentTriage risk with report evidence and project context.Review findings
ReportsARM/unit-test reports where availableCurrentRun template-focused checks when the project and backend support them.Report types
AI workspaceGrounded project chatCurrentAsk questions against project metadata, graph data, source inputs, and saved reports.Agent rules
CLIAgentic CLI workflowsCurrentConfigure profiles, create projects, run reports, ask grounded questions, download outputs, and open deeplinks.CLI overview
Agent integrationMCP serverCurrentExpose CloudEval project, report, billing, open-url, and capability tools to MCP-compatible agents.Agent rules
Agent integrationllms.txt and llms-full.txtCurrentGive external agents machine-readable product, CLI, grounding, and limitation context.LLM context
CollaborationShare links, embeds, and invited rolesCurrentShare read-only project views, embed snippets, or collaborate with named users.Sharing
BillingCredits, plan visibility, and CLI billing summariesCurrentInspect usage, credits, plans, ledger entries, invoices, top-ups, and billing deeplinks.Plans and billing
Editor workflowVS Code sidebar for CloudEval projects and findingsIn progressReview projects, resources, reports, and findings without leaving the editor.Roadmap
Editor workflowInline ARM/Bicep diagnostics and CodeLens actionsIn progressSee IaC risks in context, then explain, evaluate, or draft fixes from the editor.Roadmap
Editor workflowCloudEval MCP tools for VS Code agentsIn progressLet editor agents answer with CloudEval project, graph, and report context.Agent rules
Pull requestsRepo scanning and PR diagram diffsPlannedShow architecture, risk, and cost impact before infrastructure changes merge.Roadmap
Pull requestsGitHub Checks and CI risk gatesPlannedAnnotate pull requests and block high-risk changes with configurable thresholds.Roadmap
DiagnosticsSnapshot drift and graph diffPlannedCompare project snapshots to see what changed and which risks moved.Roadmap
DiagnosticsBlast radius and risk-path explorationPlannedTrace dependencies, identities, network paths, exposure, data access, and cost impact.Roadmap
Provider coverageAWS, GCP, Terraform, CloudFormation, Kubernetes, and telemetry evidencePlannedBroader coverage with explicit parser, provider, rule, and evidence labels.Cloud support
RemediationRanked fixes, IaC patches, PRs, waivers, owners, and evidence exportsPlannedTurn findings into reviewable change proposals with governance context.Roadmap
Provider coverageAWS and GCP live connection parityLimitedDo not assume full Azure parity today. Treat non-Azure workflows as future or limited until documented otherwise.Cloud support
CommerceTeam plan purchase and enterprise self-serve checkoutLimitedSome commercial surfaces may be visible before full checkout availability.Plans and billing

​
How to use this map

  1. Start with Current rows when planning a real rollout.
  2. Use In progress rows for near-term pilots and design discussions.
  3. Use Planned rows to understand direction, not to make delivery commitments.
  4. Check Limited rows before assuming provider, billing, or integration parity.

​
Common mistakes

  • Treating roadmap rows as available product behavior.
  • Assuming AWS, GCP, Terraform, CloudFormation, or Kubernetes support matches Azure support.
  • Hard-coding CLI commands without first running cloudeval capabilities --format json.
  • Registering MCP broadly when a focused toolset such as readonly, projects, reports, or billing is enough.

​
Tips

Last modified on May 5, 2026