Track Savings Plan and RI purchases, expirations and renewals
Provider events put commitment purchases, marketplace renewals and SKU price changes on the cost timeline, so nothing expires silently.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
# finops
Costory
APP
Yes: a 1-year RI for 6× r6g.2xlarge (RDS, Checkout) expired on Sep 28. On-demand RDS spend has risen €1,450/week since. Renewal options are in the Savings Plan coverage dashboard.
FinOps renews, resizes or lets it lapse.
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
A commitment expires or a renewal posts.
Costory investigates
01
Capture provider events
Savings Plans, RIs, marketplace renewals and SKU price changes are tracked automatically.
02
Overlay on charts
Events appear on cost charts and dashboards.
03
Alert
Get notified when uncovered spend rises after an expiry.
04
Explain
Claude links cost jumps to the events behind them.
Where you see it
Claude
You decide
FinOps renews, resizes or lets it lapse.
Why it matters
A Reserved Instance expires, on-demand spend jumps, and the team spends a week finding out why.
Who it’s for
FinOps leads, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
No silent expiries
Commitment changes are on the timeline.
Faster explanations
Cost jumps link to provider events.
Renewal awareness
Marketplace renewals are visible on the timeline.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
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
Coverage drops, or the steady on-demand baseline grows.
Savings Plans and Reserved Instances coverage review
The agent watches covered versus uncovered spend and utilization, and recommends where additional commitments could make sense as your steady baseline grows.
See the playbook
Costory notices
A SKU price change or marketplace renewal posts.
Catch SKU price changes and marketplace renewals
Provider events flag SKU price changes and marketplace renewals on the timeline, so unexplained increases get explained.
See the playbook
Costory notices
Spend on a team, service or account deviates from its baseline.
Investigate a cost spike and find the deploy behind it
When spend moves, the agent finds the deploy, team and service behind it, checks incidents and provider events from the same window, and posts the likely cause.
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