Lite
1 AWS account
Read-only · priced from your own bill
235 checks across every region find idle resources, rightsizing and data-transfer waste, plus a coverage analysis that sizes the Savings Plans you are missing. Each finding is priced against your own bill, so the total adds up.
Sample account · overview
There is $4.6k a month sitting idle in your accounts.
Potential saving by category
Where the money is
EC2 · idle & unused resources
3 resources · high confidence
$1.1k/mo
Bedrock · idle & unused resources
1 resource · high confidence
$648.00/mo
EC2 · reservation coverage
2 resources · medium confidence
$551.30/mo
Demo account, first scan, redrawn from the walkthrough below; not a forecast for your account.
On every plan, in every enabled region.
Every one of these is a rule that ships in the scanner, runs on every scan, and puts its own identifier on the findings it produces. The checks cover unattached EBS volumes and orphaned snapshots, idle and stopped EC2 instances, unassociated Elastic IPs, NAT gateways moving no bytes, load balancers with no healthy targets, RDS and ElastiCache instances nobody connects to, over-provisioned DynamoDB tables, idle Lambda functions, EKS and ECS waste, GPU boxes sitting warm, SageMaker endpoints and Bedrock provisioned throughput nobody calls, plus Graviton and Spot migration candidates and public IPv4 charges.
| Service family | Checks | |
|---|---|---|
| Block storage and object storage | 25 | 11% |
| EC2 and compute | 22 | 9% |
| Networking, CDN and edge | 27 | 11% |
| Databases and caches | 36 | 15% |
| Analytics, streaming and search | 26 | 11% |
| Serverless and integration | 15 | 6% |
| Machine learning and AI | 15 | 6% |
| Security and compliance | 22 | 9% |
| Observability and governance | 18 | 8% |
| Media and broadcast | 7 | 3% |
| Developer tools and CI/CD | 8 | 3% |
| IoT and edge computing | 4 | 2% |
| Communications and application services | 5 | 2% |
| Commitments | 3 | 1% |
| End-user computing | 2 | 1% |
| Built-in detection rules | 235 |
Plus Savings Plans and reserved-instance coverage, analyzed separately.
Each check is priced from the AWS Price List API for the region the resource sits in. Where a rate cannot be fetched, the finding is still raised, without a figure attached. Read the full list of AWS cost optimization checks, with rule identifiers, or how a Kostrix AWS cost audit works.
Reads what AWS already knows
How it works
Write to us with your top findings and we go through them together; you keep the report.
Idle resources are only half of an AWS bill. The other half is steady-state usage paying On-Demand rates because nobody sized a commitment for it. Kostrix measures both instruments separately, keeps their units apart, and recommends a purchase sized to the floor rather than the peak.
Savings Plans coverage is reported as a share of eligible spend and reserved-instance coverage as a share of eligible hours, because that is the unit each one is bought in. Expiry cliffs are listed as the scheduled cost increases they are, and the purchase recommendation is sized at 80 percent of the uncovered amount.
Savings Plans and reserved-instance coverage, measured separately
share of eligible HOURS · denominator 18,240 eligible instance-hours
share of eligible SPEND · denominator 12,880.00 USD of eligible spend
blended coverage 52.2% never printed
| Unattached volumes | 2,113 | volumes |
|---|---|---|
| Mean provisioned size | 16.00 | GB |
| Provisioned total | 33,808 | GB |
| gp3 storage rate, ap-south-1 | 0.0800 | USD / GB-month |
| Estimated monthly saving | 2,704.64 | USD / month |
2,113 x 16.00 GB = 33,808 GB
33,808 GB x 0.0800 USD/GB-month = 2,704.64 USD/month
2,113 unattached EBS volumes in one region, worth 2,704.64 USD a month, found on WhizzyGeeks' own AWS account. Every term that produced that number is printed beside it: the count, the mean size, the product, and the regional rate it was multiplied by.
Kostrix walks your billed line items and marks the ones no rule touched. On our own account that was 18 of 34, and those 18 appear on screen beside the savings rather than in a footnote. A quiet service is not a clean one, and a tool that hides the gap is selling a false all-clear.
What this changes
Findings pool by the action they require, so a queue of thousands of near-identical resources arrives as a single priced line. And where a measurement is simply missing, Kostrix prints that instead of a zero, because an absent measurement is not a measurement of zero.
Pooling is by account, region, rule and resource, because a resource id is not globally unique. The 2,113 unattached volumes arrive as one line, “Delete unattached EBS volumes”, with the count, the region and the monthly figure; the individual resources stay attached to the row and export with it.
When CloudWatch returns no datapoints for a region, the mean CPU utilization there is printed as “no measurement”, the region is skipped and the gap is logged. Writing 0% would have invented an idle fleet and a saving to go with it.
Kostrix reads your account and recommends. It holds no permission to change anything in it: the read-only IAM policy it runs under is published in full. For the problem searches these checks answer, see unused EBS volumes and idle AWS resources: EC2, RDS, NAT gateways and load balancers.
Pricing
Prices in US dollars, no tax. Every plan runs all 235 checks.
1 AWS account
Up to 5 AWS accounts
Up to 20 AWS accounts
The struck-through figure is the full price; the one above it is what is charged. Every plan, the free trial and how billing works.
That list is usually the most interesting output of a first scan, and it is the fastest way to tell whether an AWS cost reduction tool is being straight with you.