CLOUD INTEGRATION

GCP Cost Management: No BigQuery Export to Maintain

Cloud Billing reports are coarse; detail means exporting to BigQuery and paying per query, and reseller GCP must be recomputed as list × discount — and it’s GCP-only. Mof unifies GCP with your other clouds in one read-only table: real payable, allocation, alerts and Excel export.

GCP native · roll your own

GCP native · roll your own

Cloud Billing reports

Billing export

BigQuery

Looker Studio

SELECT SUM(cost) FROM `billing_export` WHERE …

Enable export, write SQL — and BigQuery still bills per query (~$6.25/TB)

Mof · one read-only key

Mof · one read-only key

Read-only key
Auto-sync
Full dashboard
Real payable
One table
Smart alerts
Excel export

Works out of the box — no SQL, no extra query fees

Why teams use Mof to manage GCP cost

Plenty of teams run Compute Engine, Cloud Storage, BigQuery and GKE on GCP, reading the bill either coarsely in Cloud Billing reports or by exporting to BigQuery and writing SQL. Once resources span projects — and you run other clouds too — “why did this cost more?” and “whose is this?” take several places to answer.

Mof is a FinOps platform for teams running more than one cloud — AWS, Azure and GCP alongside Alibaba, Tencent and other clouds most tools can’t reach. It connects to GCP read-only, then layers on real payable, the Resource Center, cost allocation and real-time alerts — all in one view.

Three ways to read your GCP bill — each with a catch

Cloud Billing reports, BigQuery export, invoices — each solves a piece, and each leaves a gap.

Cloud Billing reports (console)
  • No SQLCan’t write custom queries or join data
  • Limited granularityBy resource / label means exporting first
  • Hard to shareCan’t show the view to people without GCP access
  • No real-time alertsBudget alerts are separate
Billing export → BigQuery
  • Enable export firstAnd it doesn’t backfill history
  • You write SQLFinance and business teams can’t use it
  • Billed per queryBigQuery ~$6.25/TB + storage
  • No latency SLAData arrives unevenly, not real-time
Invoice / cost table (PDF)
  • Monthly totals onlyNo drill-down to resources
  • Reseller pricingRecompute real cost as list × discount
  • Static billNo trends, allocation, or alerts

How Mof solves these

Connect read-only, unify GCP with your other clouds, and fill in real payable, Resource Center, allocation and alerts.

Cloud Billing reports only skim the surface — for detail by resource or label, export to BigQuery and write SQL
Mof connects read-only and gives you a detailed dashboard on connect — drill down by project or resource, no SQL, no per-query charge.
GCP via a reseller lives in the reseller’s BigQuery, so you recompute real cost as list × discount
Mof supports custom discounts: it turns list pricing into your real payable, laying out billed, discount, saved and payable in one line.
BigQuery bills per byte scanned (~$6.25/TB), so heavy analysis on a big bill gets expensive
Mof’s dashboard and drill-downs aren’t billed per query — slice it any way you like; looking more never costs more.
Cloud Billing reports can’t be shared with finance or business teams who lack GCP access
Mof pairs clean dashboards with role-based access — finance and business teams just log in to see the costs they care about, no GCP console permissions needed.
It’s GCP-only — you organize across projects, and other clouds live elsewhere
Mof brings your GCP projects together with Alibaba Cloud, Tencent Cloud, Huawei Cloud and more — one table to view and compare.
To find waste, you check resources, utilization, cost and recommendations separately
Mof’s Resource Center shows it in one place: inventory + utilization (P95) + real cost per resource + over-provisioned / idle / orphaned / stopped, across projects and clouds.
Splitting shared cost is hard, and exports still need cleanup
Mof does showback by team / project / label, splitting shared resources by your rules — then exports to Excel that finance can book directly.

GCP native vs Mof

DimensionGCP nativeMof
Detail / drill-downExport to BigQuery, write SQLDetailed dashboard on connect
Analysis costBigQuery ~$6.25/TB per queryDashboard / drill-down not billed per query
Data latencyExport has no latency SLASynced, near real-time
Learning curveEnable export, know SQLWorks out of the box, for finance & teams
Real payableReseller: recompute list × discountCustom discounts → real payable
Share / accessReports hard to share without accessRole-based access, finance & business log in
Multi-project / cloudGCP-onlyMany projects + multi-cloud in one table
AlertsNo Slack / email / IM pushReal-time alerts to Slack, email & IM
Resource + usage + costViewed separatelyResource Center: inventory + P95 + payable + waste, cross-cloud
Allocation / labelsNative labels onlyShowback + virtual tags, Excel export
Anomaly detectionBasicHolt-Winters real-time alerts

GCP cost management FAQ

How is Mof different from GCP Cloud Billing and BigQuery export?

Cloud Billing reports only skim the surface; for detail you export to BigQuery, write SQL and pay per query. Mof connects read-only and produces a detailed dashboard — no SQL, no per-query charge — then adds real payable (custom discounts), the Resource Center, cost allocation and alerts, and puts your other clouds in the same view.

For GCP bought through a reseller, can Mof show the real payable?

Yes. Reseller GCP data often sits in the reseller’s BigQuery and must be recomputed as list × discount. Mof supports custom discounts to compute the real payable directly, and clearly shows billed, discount, saved and payable.

How does Mof connect to GCP billing data? Is it safe?

Through a GCP service account with read-only permissions (or Billing export / BigQuery views per our docs). Mof reads billing and resources only — it needs no write access and changes nothing in your GCP project.

Do I still pay BigQuery query fees with Mof?

You don’t pay extra BigQuery query fees to view or drill into cost in Mof. Mof syncs the bill in and analyzes it in its own dashboard — separate from running SQL repeatedly in your BigQuery.

Which GCP services does it cover? Does it support label-based allocation?

Compute Engine, Cloud Storage, BigQuery, GKE, Cloud SQL, networking and other major line items sync automatically. Allocation reuses your GCP labels and project structure, and untagged shared resources can be split by ratio or custom rules.