Find over-requested Kubernetes workloads and right-size requests
Measure the gap between requested and available CPU and memory, convert it to cost, and get request changes per deployment.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
What did idle and over-requested capacity cost us last month by cluster and node pool?
prod-eu: €8,100 idle last month (14%). Top over-requester: search-indexer requests 8 vCPU, p95 usage 2.1 vCPU. Suggested request: 3 vCPU. Estimated impact: €1,200/month once the node pool scales down.
Service owners update requests; Platform watches the node pool shrink.
Playbook
What the agent does
From what Costory notices to what you decide. Costory suggests the next step in conversation, and you decide whether to go ahead.
Costory notices
Idle capacity in a node pool stays above your threshold.
Costory investigates
01
Measure waste
Waste is the gap between available node capacity and requested CPU and memory, converted to cost.
02
Find over-requesters
Rank deployments by requested versus used resources.
03
Propose new requests
Claude suggests request values per deployment, with the usage evidence.
04
Track the result
Waste by node pool on a dashboard, before and after.
Where you see it
Claude
You decide
Service owners update requests; Platform watches the node pool shrink.
Why it matters
Kubernetes waste hides in requests nobody revisits. Nodes look full while pods use a fraction of what they reserve.
Who it’s for
Platform teams, Kubernetes owners
Where it runs
Claude · Slack
What you get
What lands in front of your team
Waste in euros
Idle capacity priced per node pool.
Per-deployment fixes
Concrete request changes with evidence.
Before and after
Measure what changed once teams ship it.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Measure
What did idle and over-requested capacity cost us last month by cluster and node pool?
Recommend
Which deployments request at least twice the CPU they use? Propose new requests and the monthly impact.
FAQ
Questions about this playbook
Does Costory guarantee savings?
No. The agent investigates and recommends with the evidence attached; your team decides what to change. Impact figures are estimates based on your own data.
How long does this playbook take to set up?
Connecting your billing data and the Costory MCP takes under 30 minutes with Terraform or CloudFormation. The playbook itself takes minutes: pick the scope, the trigger and the Slack channel. The first billing data lands the next day, and the agent starts from there.
Can we adjust what the agent does?
Yes. You choose the trigger, the scope (team, service, environment), the channel and the format, and you can pause or change it at any time.
Does Costory change anything in our cloud accounts?
No. Costory reads billing exports and the metrics you connect, and has no write access to your cloud. Actions it takes create Costory objects only: alerts, reports, dashboards and events. Your team stays in control of every change.
Step-by-step guide in the Costory docs
Related playbooks
Run these alongside it
Costory notices
Every day, for every cluster and namespace.
Kubernetes cost allocation by namespace, team and workload
Break EKS, GKE and AKS costs down by cluster, namespace and workload, and roll them up to teams.
See the playbook
Costory notices
A service runs well below its capacity for 30 days.
Rightsizing recommendations grounded in real usage
The agent compares what you pay for compute with what services actually use in CloudWatch or Datadog, then recommends instance sizes to the owning team, with the deploy history attached.
See the playbook
Costory notices
Daily, as Datadog usage and the EKS bill refresh.
Dynamic cost reallocation for EKS using Datadog usage
Split shared EKS cluster costs across teams in proportion to what each team's workloads actually use, measured in Datadog.
See the playbook
Put this playbook on call
Included in every plan, from €250/month. 30-day free trial: connect in under 30 minutes, get your first optimization recommendation the next day.
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
Setup
About 30 minutes
Data residency
EU
Access
Read-only on your cloud