Your org, every account
Connect many cloud accounts under one workspace. Findings, cost, tag compliance, and remediation are all attributed per account, with a cross-account portfolio view and a per-account filter.
Treating a cloud account as the whole tenant breaks the moment you have more than one. You can’t compare accounts, attribute waste, or remediate the right account without a real account model.
Built to do the work, not just show it
Org → N accounts
A first-class account model: add, remove, and set a primary — many accounts per workspace.
True per-account attribution
Each finding, cost row, and execution is stamped with its source account.
Cross-account portfolio
Roll up spend and savings across accounts, or filter to one from the header.
Per-account remediation
Actions assume the specific account’s cross-account role — not always the primary.
From signal to result
Add accounts
Connect each AWS account / GCP project to the workspace.
Attribute
The pipeline collects per account and stamps every record.
Compare & act
View the portfolio or a single account, and remediate the right one.
- Deleting one account no longer tombstones the whole workspace.
- The account selector renders only for multi-account workspaces, so single-account stays simple.
- Per-account cross-account roles + External IDs keep isolation intact.
Questions
Is there a limit on accounts?
No architectural limit — the workspace holds N cloud accounts, each attributed independently.
Can I see just one account?
Yes — a header selector scopes findings and cost to a single account, or show the whole portfolio.