Cloud
Google Cloud costs, allocated and explained
BigQuery billing export with detailed usage (+ CUD metadata)
How Costory connects to Google Cloud
Costory ingests Google Cloud through BigQuery billing export with detailed usage (+ CUD metadata). Google Cloud spend is normalized into the same cost model as your other providers and allocated with projects, labels, CUD metadata, Virtual Dimensions.
Questions you can ask
“Which GCP projects drove this month's increase?”
“Explain our spend-based CUD coverage and what is uncovered.”
“Send a weekly Slack report of the GCP services that moved.”
Good to know
Google's official Cloud Billing MCP exposes accounts, IAM and SKU prices, not your spend.
Official tooling
Google Cloud also has its own tooling: Google Cloud Billing MCP (no spend data). Costory adds cross-provider allocation and event context on top. Compare options.
Use Google Cloud with your AI assistant
Setup guide: Google Cloud in the Costory docs.
In Costory
Google Cloud cost in the product
Screenshots from the Costory app with this integration connected.
GCP spend overview dashboard generated with Ask Costory
BigQuery live table as an external metric next to cost
Cost by resource name, graph and top flop, trailing 7 days
Skills
Skills that use Google Cloud
What the Costory agent can watch, investigate and report on for you, with this in the loop.
All skills
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 skill
Costory notices
Spend on a team, service or account deviates from its baseline.
Investigate a cost spike and find the deploy behind it
When spend moves, the agent finds the deploy, team and service behind it, checks incidents and provider events from the same window, and posts the likely cause.
See the skill
Costory notices
An anomaly is detected, any time of day.
Investigate anomalies in a Slack thread with Costory
When an alert fires in #finops or a team channel, reply in the thread and @Costory investigates: which team, which service, which deploy.
See the skill
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 skill
Costory notices
A shared service's cost grows, or a new team starts using it.
Split shared infrastructure costs by actual usage
Allocate shared databases, networking and platform services to the teams that use them, based on real usage metrics.
See the skill
Costory notices
Every day, for every cluster and namespace.
Kubernetes cost allocation by namespace, team and workload
Break EKS, GKE and AKS costs down by cluster, namespace and workload, and roll them up to teams.
See the skill

Connect in under 30 minutes, get your first optimization recommendation the next day.
30-day free trial. Plans from €250/month, billed annually. We recommend Team (€600/month) once more than one team uses Costory.
First optimization recommendation
The next day
PRICE
From 250€/month, never a % of your bill
Setup
Under 30 minutes
Data residency
EU
Access
Read-only on your cloud
From 250€/month, never a % of your bill. 30 days free, no credit card.



