FinOps is an operational framework for maximizing cloud cost and business value together. This article walks through implementing FinOps on GCP across the three stages: Inform / Optimize / Operate.
| Stage | Goal | GCP Tools |
|---|---|---|
| Inform | Visibility and allocation | Billing Reports, BQ export, Looker Studio |
| Optimize | Recommendations and execution | Recommender API, Active Assist, CUD planning |
| Operate | Continuous improvement and governance | Budget alerts, quota limits, policy constraints |
# Cloud Billing → Billing Export → BigQuery 有効化 # 結果: <project>.<dataset>.gcp_billing_export_v1_<billing_id> -- 月別サービス別コスト SELECT invoice.month, service.description AS service, SUM(cost) AS total_cost, SUM(CAST(usage.amount AS NUMERIC)) AS usage, usage.unit AS unit FROM `my-project.billing.gcp_billing_export_v1_BILLING_ID` WHERE invoice.month = '202605' GROUP BY 1, 2, unit ORDER BY total_cost DESC;
env (prod/staging/dev), team, app, cost-center| Category | What it recommends |
|---|---|
| VM Rightsizing | Over-provisioned vCPU/memory |
| Idle VM | VMs idle for 14+ days |
| Idle Disk | Unmounted disks |
| Commitment | CUD estimates (based on the last 30 days) |
| BigQuery Query | High-scan / high-cost queries |
| Cloud SQL Idle | Low-utilization instances |
| GKE Cost Optimization | Right-sizing and bin packing suggestions |
# Terraform でプロジェクトごとに Budget
resource "google_billing_budget" "team_alpha" {
billing_account = "BILLING_ID"
display_name = "Team Alpha Budget"
budget_filter {
projects = ["projects/team-alpha-prod"]
labels = { team = "alpha" }
}
amount {
specified_amount {
currency_code = "USD"
units = "5000"
}
}
threshold_rules { threshold_percent = 0.5 }
threshold_rules { threshold_percent = 0.9 }
threshold_rules { threshold_percent = 1.0 }
all_updates_rule {
pubsub_topic = google_pubsub_topic.budget_alerts.id
}
}What is FinOps?
A collaborative framework for maximizing cost and value in cloud usage. The name combines Finance and DevOps. Standardized by the FinOps Foundation around a 3-stage maturity model: Inform / Optimize / Operate.
What are the main FinOps tools on GCP?
Cloud Billing Reports, Budget alerts, BigQuery billing export, Looker Studio dashboards, Recommender API, Active Assist, and the Pricing Calculator.
What is BigQuery billing export?
A daily export of all GCP billing data into BigQuery tables. Two variants (Standard and Detailed) let you analyze costs with SQL at the resource ID, label, and SKU level.
How do labels enable cost allocation?
Attach labels such as env / team / project / app to resources, then JOIN those labels through the billing export to aggregate costs by org unit. This is the foundation of FinOps.
What is show-back vs. charge-back?
Show-back means making each team's costs visible (transparency); charge-back means actually billing them internally (accountability). GCP supports both via labels plus the BigQuery export.
What is Active Assist?
GCP's AI-driven optimization service. It bundles the Recommender API (cost), Policy Analyzer, and Security Insights, and generates monthly reports.
Should we join the FinOps Foundation?
Recommended for organizations with large cloud spend (more than a few million USD per year). Membership unlocks the FinOps Certified Practitioner (FOCP) credential, community access, and benchmarks.
What is the FOCUS Spec?
A standard schema for cloud billing data defined by the FinOps Foundation (2024 onward). It lets you analyze GCP, AWS, and Azure in a unified format and is essential for multi-cloud FinOps.
Related Articles: FinOps and Cost Management
Terraform on GCP 完全ガイド|IaC・Provider・Workload Identity・GitHub Actions (2026)
Google Cloud で Terraform を使う IaC 完全ガイド。Google Cloud Provider / Beta、State 管理 (gcs バックエンド)、Workload Identity Federation、Module 設計、GitHub Actions CI、Infracost、Config Connector を 2026 年最新版で網羅。
GCP Professional Cloud Developer (PCD) 完全ガイド|Cloud Run・GKE・CI/CD・APM
Google Cloud Professional Cloud Developer の試験範囲、Cloud Run / GKE / Cloud Build / Cloud Trace、AWS DVA / Azure AZ-204 比較、学習ロードマップを徹底解説。
GCP 環境構築 完全チュートリアル|アカウント・組織・IAM・Billing 初期設定 (2026)
Google Cloud (GCP) の環境構築を 0 から完全網羅。アカウント作成、$300 クレジット、Organization / Folder / Project 設計、Billing アラート、IAM 設計、API 有効化、Cloud Shell、リージョン選定を 2026 年最新版で解説。
Google Cloud (GCP) 認定資格ロードマップ 2026 完全版|全 15 試験を体系化
Google Cloud 認定資格 全 15 試験 (Foundational 2 + Associate 3 + Professional 10) の 2026 年版ロードマップ。14/15 試験が日本語対応、Generative AI Leader (2025-05 新)・PMLE 2026-06 新版、AWS/Azure/GCP シェア比較、役割別ルートを日本語で整理。
Note: Google Cloud is a trademark of Google LLC, and the FOCUS Spec is a registered specification of the FinOps Foundation. For the latest information, see the FinOps Foundation official site.
Practice with certification-focused question sets
Visit the GCP exam prep pageNicheeLab Editorial Team
NicheeLab editorial team focused on data engineering and cloud certification learning. Content is structured around practical study needs and official exam domains.
Google Cloud Certification Roadmap (2026)
Choose your GCP certification path — Foundational, Associate...
CDL Cloud Digital Leader: Complete Exam Guide (2026)
Pass the Cloud Digital Leader exam — cloud business value, G...
GAIL Generative AI Leader: Complete Exam Guide (2026)
Pass the Generative AI Leader exam — Gemini, Vertex AI, Work...
Vertex AI Fundamentals for GCP Certs (2026)
Vertex AI basics every cert candidate needs — Workbench, Pip...
Associate Cloud Engineer (ACE): Complete Guide (2026)
Pass the Associate Cloud Engineer exam — Console, gcloud, pr...