Split production and non-production costs automatically
Allocate every cost line to prod, staging, dev or sandbox using account names, projects, clusters and labels.
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 new account, project or cluster appears in billing.
Costory investigates
01
Use existing metadata
Account names, project IDs, cluster names and env labels are all candidates.
02
Write environment rules
A virtual dimension maps them to prod, staging, dev and sandbox.
03
Backtest
Check allocation coverage before publishing.
04
Report
Prod vs R&D trend in a monthly report.
Where you see it
Claude
You decide
Platform confirms the environment mapping for new resources.
Why it matters
Leadership asks what production really costs and how much goes to R&D environments. Without a consistent environment dimension, every answer is a one-off spreadsheet.
Who it’s for
CTOs, platform leads, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
Prod vs R&D clarity
One trusted split for leadership and finance.
No manual mapping
Rules keep up as new accounts appear.
Trends
Spot non-production creep early.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Build
Create an Environment dimension from account names, GCP projects and cluster names. What share of spend is production?
FAQ
Questions about this playbook
What if our tagging is incomplete?
Costory's Virtual Dimensions allocate with rules on accounts, projects, names and partial tags, so you don't need perfect tagging to start. Shared and untagged cost is reallocated dynamically using the metrics you already have (Datadog, Tsuga, BigQuery, Snowflake and more), and the allocation stays consistent as usage moves.
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
The unallocated bucket grows above your threshold.
Allocate cloud costs without perfect tagging
Map accounts, projects, resource names and partial tags to teams with rules, instead of waiting for a tagging project to finish.
See the playbook
Costory notices
Unattached volumes or growing snapshots are detected.
Find unattached volumes, underused disks and growing backups
Surface storage waste and idle resources by owner, so each team gets a short cleanup list with the cost of doing nothing.
See the playbook
Costory notices
Quarter end, or before a board meeting.
A board and exec cost pack in minutes
Total spend trend, top drivers, budget progress, unit costs and month-over-month comparison in one executive view.
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