Price bursty workloads with hourly cost granularity
Use hourly cost data to measure bursty jobs, price each event or batch, and connect optimization work to per-event 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 batch run or live event costs more than usual.
Costory investigates
01
Hourly cost
Query costs at hourly granularity.
02
Mark the events
Push hourly custom metrics or events for each run or live event.
03
Price each run
Cost per job, per broadcast or per campaign.
04
Optimize
Compare runs before and after changes.
Where you see it
Claude
You decide
The team adjusts scheduling or scaling.
Why it matters
Daily totals blur batch jobs, campaigns and live events. Hourly data shows what one run actually costs.
Who it’s for
Data engineers, platform teams, product teams with live events
Where it runs
Claude · Slack
What you get
What lands in front of your team
Per-run cost
Batch and event costs made visible.
Better scheduling
See when runs are most expensive.
Proof of optimization
Before and after, per run.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Compare
Compare the cost of last Saturday's live event with the previous one, per 1,000 viewers.
FAQ
Questions about this playbook
Where do business metrics come from?
From Amplitude, BigQuery, Snowflake, Google Sheets, S3, Datadog, CloudWatch or metrics you push to Costory's API.
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
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
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
Monthly, or when a unit cost drifts beyond your threshold.
Track cost per customer, per request or per active user
Combine allocated cloud cost with your business and usage metrics to build unit costs that leadership can track over time.
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