Dashboards
A chart of the problem.
Cost dashboards tell you spend went up. They do not tell you which resource did it, who owns it, or whether it is safe to touch.
A SpendShrink finding names the resource and shows the billing lines behind it.
00AWS spend, owned
Your AWS bill keeps climbing.Nobody owns the fix.
The dashboard shows the curve. The recommendation lands in a ticket. Nobody picks it up, and next month the bill is higher. SpendShrink finds the waste, prices it from your own billing lines, and opens the Terraform change for your engineers to merge.
- Finds
- 24 detectors
- Proves
- Your own billing lines
- Fixes
- Terraform merge requests
- Costs
- $49.99 or 1% of spend
Fig. 01 / From bill line to merged fix
SpendShrink finds the waste, proves it, and writes the fix. Your engineers merge it.
SpendShrink / How it works01Why the bill keeps growing
Most cost tools show you the problem.Then they stop.
If you run AWS for a growing company without a FinOps team, you know the pattern. These are the three places savings usually die.
Tickets
A recommendation nobody picks up.
The advice lands in the backlog as a vague task. Someone still has to write the Terraform change, so it waits behind feature work, every sprint.
With SpendShrink the change arrives as a merge request, ready to review.
Savings share
A vendor paid on the estimate.
Tools that take a cut of what they say you saved earn more when the estimate is bigger. That is not an incentive to be accurate.
SpendShrink charges a flat rule on your spend. We earn the same either way.
02What SpendShrink does
Find it. Price it.Fix it.
Four steps, the same every time, from a line on your bill to a change in your repository.
Find
24 detectors
Idle, oversized, orphaned and mispriced resources across compute, storage, databases, network and commitments.
- Idle NAT gateways and load balancers
- Unattached volumes and forgotten snapshots
- Old-generation instances and nodes
- Commitment gaps and expiries
Runs on your real usage
Price
Priced from your own bill.
Every finding is priced from your FOCUS billing lines and usage history, as a low and high monthly range.
- The exact billing lines behind it
- Usage over the window it looked at
- Assumptions written down
- Unknown when the data is thin
Every figure traceable
Fix
A Terraform merge request.
If the resource lives in a connected repository, SpendShrink writes the change, checks it and opens the merge request.
- GitHub and GitLab
- terraform fmt and validate first
- A CLI runbook when it is not in Terraform
- Nothing changes until you merge
Your engineers stay in charge
Prove
A ledger finance can trust.
Estimates, merged changes and measured savings are kept apart. A saving only counts once your bill shows it.
- An owner and approval on every finding
- Comments and links to your tickets
- Validation after the change ships
- Daily spend signals against a 28-day baseline
Saved means it left the bill
It finds the NAT gateway nobody remembers creating.It prices it from your own billing lines.It writes the Terraform change.Your engineers review it and merge.
You keep the savings. All of them.
03By the numbers
Built to be checked.Every number counted.
These figures come straight from the SpendShrink source code, and a test recounts them before every release.
- Detectors
- 24
Checks for idle, oversized and forgotten AWS resources.
- FOCUS columns
- 60
Billing columns read from the cost export AWS writes for you.
- Fix runbooks
- 25
Resource types with a ready console path and CLI command.
- Test files
- 144
Guarding the backend, worker, scheduler and shared library.
Counted from the SpendShrink source code, October 2026.
04Who it is for
Built for the peoplewho own the bill.
Two kinds of teams get the most out of SpendShrink: engineers who own AWS spend on top of everything else, and partners who own it for their clients.
Engineering teams
You own AWS spend, and it is not your only job.
For the platform lead or engineering manager at a company spending roughly $5,000 to $500,000 a month on AWS, with no FinOps team.
- Findings ranked by what they are worth
- Fixes as merge requests, not homework
- Budgets and alerts before the month closes
- Plain-language answers about your own bill
From $49.99 a month
MSPs and consultancies
You run AWS for several clients.
A partner portal keeps each client as its own business, with its own AWS accounts, users, budgets and reports.
- Every client kept separate
- Set up and review each client's accounts
- Budgets, alerts and reports per client
- One partner login for the whole book
Partner portal in the app
05Pricing
$49.99 a month,or 1% of tracked spend.
Whichever is greater. No share of your savings, no seats, no tiers. The price follows the AWS spend we track, so we gain nothing by inflating an estimate.
| Monthly AWS spend | SpendShrink |
|---|---|
| $2,000 | $49.99 |
| $10,000 | $100 |
| $25,000 | $250 |
| $100,000 | $1,000 |
--Get started
Stop paying forwhat nobody uses.
Connect one AWS account. The first findings arrive once AWS delivers your first billing export, usually within a day.