Cost impact of every deploy, from GitHub events
Capture deploys, PR merges and releases from GitHub or your CI/CD pipeline, and see which ones changed cost.
Runs in
Claude · Slack
First optimization recommendation
The next day
ROI
Pays for itself with the first recommendation you act on
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 deploy is followed by a cost change on the same service.
Context used
Remembered
Costory investigates
01
Connect events
The GitHub integration captures deploys, PR merges and releases; CI/CD pipelines post events through the Events API.
02
Overlay
Events appear as markers on cost charts.
03
Compare
Cost before and after each deploy on the affected service.
04
Notify
Post notable deploy impacts to the team channel.
Where you see it
Claude
You decide
The team that shipped decides whether it's expected.
Why it matters
Engineers ship dozens of changes a week. When cost moves, nobody knows which change did it.
Who it’s for
Engineering managers, platform teams, developers
Where it runs
Claude · Slack
What you get
What lands in front of your team
Deploy-level accountability
Know which change moved cost.
No extra work
Events flow in from GitHub and CI/CD.
Faster fixes
Regressions caught while the change is fresh.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Check
Which deploys in the last 30 days were followed by a cost change of more than 10% on the same service?
FAQ
Questions about this playbook
Which agents and assistants work with Costory?
Claude, Claude Code, Cursor, VS Code with GitHub Copilot and Dust connect to the hosted Costory MCP server with OAuth.
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
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
Costory notices
An optimization is logged as shipped.
Measure the impact of every optimization you ship
Log each optimization as an event and compare cost before and after, so the team can show what each change saved.
See the playbook
Costory notices
A release changes a service's cost per request.
Cost per API request with Datadog or CloudWatch metrics
Divide a service's allocated cost by its request volume from Datadog or CloudWatch, and track it release after release.
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