GCP cost guides
Use this hub when the provider boundary is the real question, not just the category label.
What this hub helps you route
Start here when a GCP-specific path like inter-zone traffic, serverless retries, or managed analytics/storage behavior needs to be separated before you can trust the estimate.
- Pick the next guide by boundary first, not by whichever service name looks closest.
- Move to calculators when you already have request, GB, GB-month, or runtime inputs.
- Use the service guide directly once the provider-specific unit path is clear enough to model.
GCP-specific estimate failures
GCP estimates usually drift when inter-zone transfer, serverless retry multiplication, and logging growth are modeled after the main service price instead of before it.
- Transfer paths are blended instead of separating internet, inter-zone, and cross-region movement.
- Serverless estimates stop at successful requests and ignore retries, cold-start mitigation, or timeout spillover.
- Observability is budgeted as a side effect even when label cardinality and query patterns are driving spend.
- Storage and analytics workloads skip lifecycle, retention, and replay/backfill scenarios.
Best first routes inside GCP
Networking and delivery
Use these when transfer boundaries, traffic processed, or origin-vs-edge behavior are the real pricing problem.
Runtime, analytics, and data services
Use these when managed runtime choice, workload shape, worker scaling, or database/storage growth is what actually moves the bill.
Observability, Kubernetes, and messaging
Use these when GKE overhead, logging growth, monitoring cardinality, or message delivery amplification is the part you need to validate next.
When to skip this hub
- If the estimate problem is still generic storage, egress, or logging math, start from the broader category guide.
- If you already know the exact GCP service and cost unit, go straight to that page.
- If you already have inputs, use GCP calculators first and return here for boundary review.