GCP
Google Cloud projects, same control plane.
Service-account access, inventory, Compute Engine, Cloud Storage, Terraform stacks, Cloud SQL, Cloud DNS, monitoring, cost from your billing export, Cloud Functions and Artifact Registry, and GKE clusters that become Kubernetes projects.
THE MANUAL WAY
Where GCP projects get hard to track.
THE TWENTY PROJECTS
Every team got its own GCP project, which was the right call. Now finding a VM means knowing which of twenty projects to open first.
THE BILL WITHOUT AN ANSWER
Spend jumped this month. The billing export has the answer, in a BigQuery table nobody on the ops side knows how to query.
THE KEY FILE
A service-account JSON key was committed to a repository two years ago. It still works, and nobody is sure what else uses it.
WHAT TALOS DOES
GCP, without twenty browser tabs.
Service-account access
Keys stored encrypted per account and used only for the length of a job, never written to a host.
Cross-project inventory
Compute, storage, databases, DNS and more swept into one view, including what was created outside Talos.
Compute and storage
Start, stop, resize and inspect instances; manage Cloud Storage buckets and objects as tracked operations.
Stacks with drift
Terraform stacks plan and apply as jobs, with drift detected against what is deployed.
Cost from the billing export
Talos queries your BigQuery billing export by service and day, and labels its forecast a run-rate estimate. No export configured means it says so, rather than showing zero.
Cloud SQL, DNS and Functions
Cloud SQL instances, Cloud DNS zones and records, and Cloud Functions, alongside Cloud Monitoring metrics and alert policies.
HOW IT RUNS
Every action is a tracked job.
WHAT MAKES THIS DIFFERENT
An honest number, or none at all.
GCP has no cost query API in the way AWS and Azure do: the source of truth is the billing export you configure into BigQuery. Talos finds the export table and reads it. Where no export exists, the cost page shows a setup card instead of a zero, because a zero would read as "this costs nothing". The forecast is clearly labelled as a run-rate estimate.
RELATED CAPABILITIES
Attach one project, read-only.
The first sweep writes nothing. Point it at the billing export too, and cost shows up beside the resources.