Snowflake cost by warehouse, team and workload
Allocate Snowflake credits to teams and workloads using warehouses and query history, next to your cloud bill.
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
Daily, as Snowflake usage refreshes.
Context used
Remembered
Costory investigates
01
Connect
Key-pair authentication and a reusable Snowflake integration.
02
Usage in currency
Daily usage in currency plus warehouse and query history.
03
Allocate
Warehouses and roles mapped to teams.
04
Report
Per-team Snowflake cost in showback.
Where you see it
Claude
You decide
Data platform leads confirm warehouse ownership.
Why it matters
Snowflake is often one of the largest bills after the cloud provider, and one of the least allocated.
Who it’s for
Data platform teams, finance
Where it runs
Claude · Slack
What you get
What lands in front of your team
Allocated credits
By team and workload.
Next to cloud
One cost model.
Showback-ready
Included in team reports.
Sources and assistants
What it connects
Data sources
Example prompts
Or drive it yourself
FAQ
Questions about this playbook
Which platforms are supported?
Snowflake, BigQuery, Datadog, Confluent, Aiven, Elastic Cloud, ClickHouse, Cloudflare and more, plus any FOCUS-formatted billing data in BigQuery.
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 warehouse's idle share or top query cost rises.
Snowflake warehouse review: sizing, idle time and expensive queries
Use warehouse and query history from Snowflake account usage to find oversized warehouses, idle credits and the queries that cost the most.
See the playbook
Costory notices
A dbt model's cost jumps or a new expensive model appears.
BigQuery cost by dbt model, package and team
Label BigQuery jobs with dbt metadata and allocate processing and storage costs to models, packages and owners.
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