Complete-estate visibility
See what exists, how fresh it is, and how much is governed by IaC.
Cloud Inventory separates loading, empty, denied, partial, stale, and complete scopes. It uses complete discovery runs to retire absent resources, derives IaC coverage from desired-state identity matches, and keeps exports, saved views, sorting, filters, and aggregation bound to the full organization-scoped result set.
Design
Prompt, code, pattern, or live context
Review
Cost, threat, scale, and compliance
Document
CoDocs, HyperDocs, and share links
Govern
Discovery, drift, and IaC continuity
Complete-query semantics
Filter, sort, paginate, aggregate, and export the complete server-side scope rather than one client page.
Freshness and permission evidence
See account, region, service, resource-type, pagination, and permission gaps before trusting inventory claims.
Identity-based IaC coverage
Distinguish managed, unmanaged, and unknown resources using real desired-state matches.
How it works
The workflow behind Cloud Inventory.
Each step exists to reduce time-to-clarity for technical teams without forcing them into a separate diagramming or documentation toolchain.
Step 1
Select the estate
Choose provider, account, region, service, and evidence boundaries without triggering a scan.
Step 2
Inspect the asset atlas
Review resources alongside freshness, completeness, age, service composition, and IaC coverage.
Step 3
Route governed work
Save the view, export all matching rows, or send selected evidence into the codification queue.
Best fit
Integrations
Outputs
Related features
Explore the rest of the workflow.
Out-of-band infrastructure changes
ClickOps Detection
ClickOps Detection correlates provider events, desired-state evidence, and actual-state observations to expose changes made outside code.
Evidence-first desired-state ingestion
IaC Import
IaC Import acquires, validates, parses, analyzes, and reconciles infrastructure sources with an immutable completeness receipt.
Versioned infrastructure provenance
Infra Graph
Infra Graph builds a versioned, provenance-linked model across declared, observed, inferred, partial, and contradicted infrastructure relations.
Next step
See Cloud Inventory inside the full Architecto workflow.
Start on the free plan, then move from this feature into the larger architecture, review, and documentation flow when the team is ready.