Connect cloud cost reporting in 30 minutes, first report the next day
Connect AWS, Google Cloud, Azure and Datadog billing with Terraform or CloudFormation, then send your first report.
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
You connect your first billing export.
Costory investigates
01
Billing exports
A Terraform module or CloudFormation stack for CUR 2.0, the BigQuery billing export and Azure exports.
02
Connect in Costory
Add each source on the Integrations page.
03
Connect Slack
Invite the bot to your cost channel.
04
First report
Schedule a weekly report or ask Claude a first question.
Where you see it
Claude
You decide
You pick the channels and teams to start with.
Why it matters
FinOps projects stall at setup. Billing exports, permissions and dashboards can take weeks before anyone sees value.
Who it’s for
Platform engineers, DevOps
Where it runs
Claude · Slack
What you get
What lands in front of your team
A fast start
Under 30 minutes with Terraform or CloudFormation.
No agents
Billing exports only.
Value the next day
A first report and first answers once the first billing data lands.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
First question
Give me an overview of our cloud spend for the last 3 months by provider and top services.
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
Every Monday at 9:00, for each team.
Weekly showback per team, posted in each team's Slack channel
Every engineering team gets its own weekly cost report in its own Slack channel, scoped to the services it owns.
See the playbook
Costory notices
A developer is about to change a service.
Cost context in your terminal with Claude Code
Connect the Costory MCP to Claude Code so the agent checks what a service costs, how it changed and who owns it before you ship a change.
See the playbook
Costory notices
Every Monday morning.
Weekly cost digest: the changes that matter, ranked by impact
Every significant cost shift ranked by impact, with an AI summary, delivered to Slack, Teams or email.
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