Google Cloud
Google Cloud cost management from your own billing export
Cloud Connects with BigQuery billing export
Costfluent reads Google Cloud cost from the detailed billing export in your BigQuery dataset, through one grant to a service account it holds for your organization. The same cost basis then feeds cost reports, budgets, allocation, insights and savings.
Permanent Free plan with no time limit
How you connect
A billing account, shared in the console or by Terraform
Console
On the Google Cloud integration page Costfluent shows the service account it created for your organization. Grant it BigQuery Data Viewer on the export dataset, enter the billing account ID, the project and the dataset, then test or connect.
Terraform
The costfluent_gcp_service_account resource returns the service account's address, the published costfluent/cost-access/gcp module grants it the role on your dataset, and the module's credentials output feeds the connection. One apply; the provider retries while a new grant takes effect.
One billing account, every project
Connect a billing account, not a project: its export already carries the cost of every project the account pays for, so one connection covers them all.
Checked before it is saved
Costfluent validates the query it will run before storing anything, so a connection that saves can read your cost. If Google does not answer during the check, the connection is saved anyway and checked again automatically.
What is read
Your cost data, from your dataset
The detailed usage cost export
The BigQuery export with the per-resource fields the standard export lacks: billing records and resource-level fields for every project the billing account pays for. Google can take a few hours to write its first rows.
A dataset you own
A BigQuery dataset in a project of yours, in the EU or US multi-region. A dedicated project keeps the grant narrow, and the connection reads that export, not application datasets.
History from the export
Connecting imports the most recent months of your plan's backfill, and the rest is collected on request, as long as the export holds rows that far back. A project alone is not the billing scope; the billing account is.
What you do with it
Google Cloud projects in reports, segments and budgets
Google Cloud cost by project, service and region
Group Google Cloud cost by project, service, region or label, filter it to the scope behind a question, and save the view for every review.
Google Cloud projects assigned to teams
Ordered rules assign Google Cloud cost to teams, products and cost centres by project, resource name or label; what no rule claims stays visible as unallocated.
Google Cloud spend against a budget
Set a budget on a saved cost report filtered to Google Cloud or one project, and follow actual spend and the forecast through the period.

What you grant
One role on one dataset, revoked by removing it
- BigQuery Data Viewer on the export dataset, and on the carbon footprint and committed use discount datasets if you share them. You can also grant the Recommender viewer roles on the projects, folders or organization whose cost recommendations Costfluent should list. Costfluent runs its queries in its own project and pays for them there: no other dataset, no jobs on your bill.
- No key is created or exchanged. The service account belongs to Costfluent, exists for your organization alone, and its address is the same every time you open the dialog.
- If your organization restricts sharing to known domains, allow the organization ID and customer ID Costfluent shows beside the address first.
- Remove the connection and the grant, or run terraform destroy, and access ends. Removing the connection erases the cost it imported; when the organization is deleted, its service account is deleted with it.
Related pages
- AWS integration
A read-only IAM role and your FOCUS Data Export in your own S3 bucket.
- Azure integration
A service principal with two read roles on the subscriptions you choose.
- Kubernetes cluster agent
Node costs distributed across namespaces by an agent you install with Helm.
- All integrations
Every cost source Costfluent reads, with its status.
- Security and data access
Where Costfluent runs, the access each connector needs and how to revoke it.
Articles on this topic
From the handbook
- Billing data and standards
Google Cloud billing export: datasets and fields
- FinOps tools and cost consoles
Google Cloud billing reports and the FinOps hub
- Google Cloud billing and pricing
Compute Engine pricing explained
- Google Cloud billing and pricing
Cloud Run and Cloud Run functions pricing
- Google Cloud billing and pricing
Google Kubernetes Engine pricing
- Google Cloud billing and pricing
Persistent Disk and Hyperdisk pricing
Start with your own Google Cloud costs
Create a Free workspace and connect your Google Cloud billing export when you are ready.
Permanent Free plan with no time limit