GCP, accounted for
GCP is frequently the third cloud: a few GKE clusters, some Cloud SQL, a data team with strong opinions about BigQuery permissions. Third clouds are exactly the ones that drift unwatched. LynxTrac onboards GCP with a service account key and keeps it in the same governance loop as AWS and Azure.
Inventory, cost, compliance, and drift work the same way across all three providers, so the third cloud stops being the neglected one.
Project inventory
GCE instances, Cloud SQL, GCS buckets with access-policy visibility, GKE clusters, GCR registries, networking, and Secret Manager, discovered across regions.
Spend you can explain
Daily cost rollups by project, region, and service, with the same budget and alerting machinery as the other providers.
One compliance posture, three clouds
The same CIS, PCI-DSS, HIPAA, and SOC 2 scans run across GCP, AWS, and Azure, with one findings workflow instead of three dashboards.
Setting it up
Create a service account with read scopes, download the key JSON, and add it as a cloud account. The key is encrypted at rest like every platform credential.
GCP audit log aggregation joins the platform-wide activity trail alongside CloudTrail and Azure Activity Log.
See it connected to your own account
The free tier covers 2 servers forever, which is enough to wire this up and judge it on your infrastructure rather than ours.