Know what your AWS Organization costs, who owns it and what is exposed.

Every account on one screen, with the verdict first and the evidence underneath. Cloud_CTRL runs in your own AWS account, can only read, and your AWS data stays there.

Ask · an example organization

You asked: What changed in spend this month?

Spend is running ahead of last month, and one account explains most of the rise.

  • Month to date is up $50,611 on the same days last month.
  • prod-core carries 64% of the rise, most of it Amazon EC2 in eu-west-1.
  • RDS followed at +$6,210, and Lambda fell.
Read fromCost ExplorerOrganizations

You asked: Which spend has no owner?

Most of the unowned spend sits in two accounts that predate your tag policy.

  • $38,402 this month carries none of the tags you declared.
  • data-lake and sandbox-legacy hold $29,110 of it.
  • 68% of taggable resources have an owner. The rest are listed by account.
Read fromAWS ConfigCost Explorer

You asked: Which account drove this month's rise?

The production account drove most of it, and the growth is compute, not storage.

  • prod-core is up $32,391 on the same days last month.
  • $27,840 of that is Amazon EC2, most of it On-Demand.
  • analytics is next, at +$9,870.
Read fromCost ExplorerOrganizations

You asked: Which commitments expire soon?

The Savings Plan carrying most of compute expires before a renewal can be priced.

  • A Compute Savings Plan at $14,200 a month ends in 17 days.
  • It covers 38% of compute spend across the organization.
  • A three-year renewal needs about 60 days to price and approve.
Read fromCost Explorer

You asked: Where are the open findings?

Exposure is concentrated, and one account has stopped reporting.

  • 61 critical and high findings are open across 24 accounts.
  • 9 are older than 30 days, all of them in two accounts.
  • sandbox-legacy has not reported to Security Hub for 6 days.
Read fromSecurity HubIAM

What it shows, in an example organization

Accounts, every member of the organization
24
Resources, with every tag on them
14,208
Months of billing, the furthest back AWS will go
14
Spend this month, against $431,508 by now last month
$482,119▲ +11.7% adverse
Spend no owner can be charged for
$38,402
Open findings, critical and high, across 24 accounts
61

Read from the systems that already hold the truth

Six pages

Each one opens with a verdict, then lets you go underneath it.

See how the CFO, the CTO and the cloud team use them

Where it runs

Cloud_CTRL runs in your AWS account, and your data stays there.

Your AWS account

Your Region · encrypted at rest

  • The screens

    Served from your own account

    One deploy, one organization. Not a seat on a platform of ours.

  • The reading

    A role you grant and revoke

    It can look at the bill and the inventory. It cannot change either.

  • The figures

    Stored where they were read

    Cached in your account, encrypted at rest.

What crosses this line

None of your AWS data. No copy of your bill, your inventory or your findings is held anywhere else.

  • Read-only
  • Your AWS account, your Region
  • Encrypted at rest in your account
  • Revocable in one action
Read how it runs, what it reads and what it keeps

From a customer

“The monthly review went from two days of work to one screen we open in the meeting.”

Northbound Payments
24
Accounts read across the organization
3
Regions with something running
March
Live since, and read every 4 hours

Services

The dashboard is free. Add the services around it when you need them.

Senior AWS architects review your environment in Office Hours. Compare the plans.

Point it at your organization and see the first answer the same afternoon.

30 minutes of one engineer · your AWS data stays in your account

Book a walkthrough