Inventory

Inventory is the searchable catalog of everything Cartography has discovered across your connected sources, normalized so the same kind of thing looks the same wherever it came from. An AWS IAM user, an Okta user, and a Google Workspace user all appear as a User; a laptop from Jamf and the same laptop from Kandji collapse into one Device. You browse by resource type without having to know which provider owns what.

The Inventory page

Open Inventory and pick a resource type from the selector at the top; each entry shows the type's icon and a live count. The types cover the breadth of your environment, grouped roughly into:

• Identity and access: users, user accounts, groups, service accounts, permission roles, API keys, and secrets.
• Compute: compute instances, containers, functions, clusters, and container registries.
• Data and network: databases, object storage, public IPs, load balancers, DNS zones, certificates, and network access controls.
• Code and endpoints: code repositories and devices.

The columns are tailored to each type: Compute Instances show provider, region, type, and state; Databases show whether they are encrypted; Object Storage shows whether a bucket is public; Certificates show the expiry date; API Keys show last used and expiry. Each type has a structured search bar (filter by id, name, provider, state, and other type-specific fields), server-side sorting, and infinite scroll. Export JSON downloads the currently loaded rows for offline review.

Resource detail

Click a row to open its detail dialog (deep-linkable, so a filtered-and-selected view is shareable). It shows a fuller set of fields than the table, plus up to three actions:

• Open in console: jump to the resource in its cloud provider's console (shown only when SubImage has a console link for it).
• Explore: open this resource in the Graph explorer with its neighbors already loaded.
• Copy object: copy the row as JSON.

The unification pays off here. Open a User and the detail lists every provider account behind that person, each with its own MFA state and last activity, so you see one identity and all its footholds in one place instead of reconciling separate provider exports.

Programmatic access

Over MCP, inventory questions run as Cypher against the graph: every inventory type is one ontology label, and the inventory-via-cypher skill maps the type to its label and query shape. That covers any resource type in the graph, not only the ones this page lists. See Connect via MCP.

To walk the relationships behind the inventory rather than browse them as tables, see the Graph explorer.