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.
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
The unallocated bucket grows above your threshold.
Costory investigates
01
Merge what exists
Dimensions merge native tags and labels across providers and normalize values like prod, production and prd.
02
Write rules
Virtual Dimensions use CEL rules (first match wins) on accounts, projects, services and names.
03
Backtest
Preview per-rule cost and allocation coverage on the last 30 days before publishing.
04
Iterate with Claude
The MCP exposes draft, preview, overlap and publish tools, so Claude can help refine the rules.
Where you see it
Claude
You decide
FinOps reviews the drafted rules and publishes them.
Why it matters
Tagging campaigns take quarters and never reach 100%. Meanwhile, nobody can say who owns a third of the bill.
Who it’s for
FinOps leads, platform teams
Where it runs
Claude · Slack
What you get
What lands in front of your team
Allocation today
Most spend gets an owner in days, not quarters.
Backtested rules
You see the impact before publishing.
Higher allocation coverage
Shared and untagged cost is reallocated by usage, and Claude points to the tags worth fixing first.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
Draft
Draft a Team virtual dimension from our AWS accounts, GCP projects and existing team tags. Show the allocation coverage.
Prioritize
Which untagged resources carry the most cost, and which usage metrics could reallocate them?
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
Weekly, or when untagged spend jumps.
Tag coverage audit: the agent finds allocation gaps and drafts the rules
Find which label keys could become dimensions, how much spend each one covers, and where untagged cost is concentrated.
See the playbook
Costory notices
A new account, project or cluster appears in billing.
Split production and non-production costs automatically
Allocate every cost line to prod, staging, dev or sandbox using account names, projects, clusters and labels.
See the playbook
Costory notices
Every week, across every connected provider.
One showback across AWS, Google Cloud, Azure, AI and data platforms
Teams see all their costs in one place, whatever the provider: cloud, Kubernetes, data platforms and LLM APIs.
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