Feature Availability

This page is the source of truth for current feature scope in public docs.

Why it matters

Teams make better rollout decisions when they can separate stable workflows from limited or planned ones.

Status labels:
Available = production-ready now
Limited = implemented but gated or partial
Planned = not generally available

Expected output: You can decide whether to adopt now, pilot with constraints, or defer.

Area	Status	Notes
ARM template parsing and graph generation	Available	Reliable baseline workflow for onboarding and analysis.
AI chat and streaming	Available	Chat-driven analysis is part of standard product workflows.
Project file management and editor save flows	Available	In-app editing and file workflows are broadly supported.
Cost report generation and history	Available	Cost reporting is available for ongoing optimization loops.
Well-Architected report generation and history	Available	Security and architecture reporting is production-ready.
Unit-test style report regeneration	Available	Regeneration workflows are available for review cycles.
Cloud connection sync workflows	Limited	Availability and depth can vary by setup and rollout.
Export format breadth (PNG/PDF/draw.io/Visio parity)	Limited	Access can vary by plan and current rollout.
Full multi-cloud feature parity	Planned	Provider parity remains an active roadmap area.
Enterprise self-serve checkout	Planned	Enterprise is typically handled through commercial process.

After using this matrix, each team should know which workflows are safe for production adoption.