| Cloud ingestion | Azure Cloud sync connections | Current | Connect an Azure subscription or resource group scope and turn it into a CloudEval project. | Connect Azure |
| IaC ingestion | Single ARM template import | Current | Upload or reference ARM JSON before deployment and evaluate it as a project. | Import ARM or Bicep |
| IaC ingestion | Multi-file ARM workspace import | Current | Preserve linked or nested ARM templates as source files and resolve them for diagrams and reports with .cloudeval/config.yaml. | IaC project config |
| IaC ingestion | Bicep review through compiled ARM JSON | Current | Compile Bicep to ARM JSON, then use the same import and report workflow. | Automate with the CLI |
| Project model | Projects, connections, files, and sharing | Current | Keep topology, source inputs, reports, collaboration, and share links together. | Projects |
| Diagrams | Interactive architecture and dependency diagrams | Current | Inspect cloud resources, relationships, layout, and resource context visually. | Diagrams and workspace views |
| Reports | Cost reports | Current | Estimate cost exposure, savings opportunities, and cost review inputs. | Run reports |
| Reports | Architecture and Well-Architected reports | Current | Review pillar scores, findings, issue counts, and architecture recommendations. | Report types |
| Reports | Evaluation coverage | Current | Understand the public-safe count of architecture checks, IaC readiness tests, cost signals, graph insights, and release quality gates. | Evaluation coverage |
| Reports | Cross-project issues inventory | Current | Triage architecture findings, cost opportunities, and unit-test failures across projects in /app/issues or with cloudeval issues list. | CLI command reference |
| Reports | Security and architecture finding review | Current | Triage risk with report evidence and project context. | Review findings |
| Reports | ARM/unit-test reports where available | Current | Run template-focused checks when the project and CloudEval service support them. | Report types |
| AI workspace | Grounded project chat | Current | Ask questions against project metadata, graph data, source inputs, and saved reports. | Agent rules |
| CLI | Agentic CLI workflows | Current | Configure profiles, create projects, run reports, ask grounded questions, download outputs, and open deeplinks. | CLI overview |
| Agent integration | MCP server | Current | Expose CloudEval project, report, billing, open-url, and capability tools to MCP-compatible agents. | Agent rules |
| Agent integration | llms.txt and llms-full.txt | Current | Give external agents machine-readable product, CLI, grounding, and limitation context. | LLM context |
| Collaboration | Share links, embeds, and invited roles | Current | Share read-only project views, embed snippets, or collaborate with named users. | Sharing |
| Billing | Credits, Pro checkout, plan visibility, and CLI billing summaries | Current | Inspect usage, credits, the enabled Day Pass and Pro plans, ledger entries, invoices, top-ups, and billing deeplinks. | Plans and billing |
| Pull requests | GitHub App repository sync | Current | Link a GitHub repository to a CloudEval project so review jobs can resolve repository, branch, commit, and source-root provenance. | GitHub repository sync |
| Pull requests | GitHub Actions composite action | Current | Run CloudEval review in CI, upload workflow artifacts, and use a scoped access key instead of hand-rolled CLI setup. | GitHub Actions integration |
| Pull requests | PR comments from CloudEval review | Current | Post or update one result comment with source provenance, report links, gate result, and drilldowns when repository permissions allow it. | GitHub Actions integration |
| Pull requests | CI job failure via configured gates | Current | Fail the workflow job when .cloudeval/config.yaml ci.gates thresholds are not satisfied. | GitHub Actions integration |
| Editor workflow | VS Code sidebar for CloudEval projects and findings | In progress | Review projects, resources, reports, and findings without leaving the editor. | Roadmap |
| Editor workflow | Inline ARM/Bicep diagnostics and CodeLens actions | In progress | See IaC risks in context, then explain, evaluate, or draft fixes from the editor. | Roadmap |
| Editor workflow | CloudEval MCP tools for VS Code agents | In progress | Let editor agents answer with CloudEval project, graph, and report context. | Agent rules |
| Pull requests | GitHub Checks UI annotations | Planned | Add richer GitHub-native annotations beyond the workflow job result and PR comment. | Roadmap |
| Pull requests | PR diagram diffs | Planned | Show architecture diffs across pull-request changes. | Roadmap |
| Pull requests | Native repo scanning without setup | Planned | Scan repositories without requiring the current GitHub App plus action workflow setup path. | Roadmap |
| Diagnostics | Snapshot drift and graph diff | Planned | Compare project snapshots to see what changed and which risks moved. | Roadmap |
| Diagnostics | Blast radius and risk-path exploration | Planned | Trace dependencies, identities, network paths, exposure, data access, and cost impact. | Roadmap |
| Provider coverage | AWS, GCP, Terraform, CloudFormation, Kubernetes, and telemetry evidence | Planned | Broader coverage with explicit parser, provider, rule, and evidence labels. | Cloud support |
| Remediation | Ranked fixes, IaC patches, PRs, waivers, owners, and evidence exports | Planned | Turn findings into reviewable change proposals with governance context. | Roadmap |
| Provider coverage | AWS and GCP live connection parity | Limited | Do not assume full Azure parity today. Treat non-Azure workflows as future or limited until documented otherwise. | Cloud support |
| Commerce | Team, Business, and enterprise self-serve checkout | Limited | Team and Business are disabled for launch unless billing configuration marks them sellable; Enterprise remains contact sales. | Plans and billing |