Your asset inventory is a spreadsheet someone updated last quarterAuditors ask what you run today
Point it at your cloud and get every resource back with its owner, its purpose, and its end-of-life date, collected live, exportable as audit evidence, and current every time you reload.
Interactive demo with sample data, no signup, no cloud account
How It Works
Connect, collect, enrich, export, on every run.
01
Connect
Short-lived, read-only credentials are minted per collection. Nothing is stored, and the inventory never needs write access to your environment.
02
Collect
The collector sweeps every supported service across every account, subscription, and project you point it at, with bounded timeouts so one slow target can't stall the run.
03
Enrich
Each resource is matched against an end-of-life reference for operating systems, database engines, and function runtimes, then scored Active, Approaching, End-of-support, or End-of-life.
04
Export
Filter to the slice an auditor asked for and export it as CSV or JSON, including any role descriptions your team has edited.
What You Can Do
Everything the inventory does.
One consolidated inventory
AWS, Azure, and GCP assets land in a single catalog rather than three. Compute, managed databases, serverless functions, object storage, caches, API gateways, audit trails, log groups, and web firewalls, side by side and filterable together.
Name and ID, type, account, role, OS or engine, version, firmware, vendor, network, subnet, zone, private and public IP, size, state, commissioned and last-boot dates, and security groups.
Every OS, database engine, and runtime is dated against a maintained EOL reference and colour-coded across four states, so unsupported software surfaces before an auditor finds it.
Query the inventory conversationally, "expired Python functions", "internet-facing compute", "databases at risk", and the matching resources filter down with a written answer attached.
The one field no API returns is what a resource is for. Draft it per resource or across the whole table with AI, edit anything, and your wording persists across reloads and rides along into exports.
Every discovered asset is marked utilised or unutilised, stopped instances, unattached disks, empty buckets, functions that have never been invoked. Decommission what nothing depends on and stop paying for it.
Upload the asset spreadsheet you already maintain and compare it against what was actually discovered. You get three lists: assets in your sheet that no longer exist, live assets missing from your sheet, and rows whose details have drifted.
Multi-account and multi-subscription
Collect from every account, subscription, and project configured for your organisation in a single pass, then scope the table to one or view them together.
Stack resource-type and lifecycle-status chips, free-text search across every field, and a commissioned-date range to isolate precisely the population a control calls for.
CSV for the auditor's workbook or JSON for your own pipeline, reflecting the current filters, a point-in-time record of what you ran and when it was captured.
Reload re-collects live rather than serving a cached snapshot, so the inventory reflects your environment as it is now, not as it was when someone last remembered to update it.