Auto-discover Compute Engine, GKE, Cloud SQL, Cloud Storage, VPC networks, firewall rules and IAM across every region of your GCP projects — in the same dashboard as AWS, Azure, OCI and VMware.
CloudVista calls Google Cloud APIs across every region and zone in each connected project, building an always-current asset inventory without agents or manual input.
Machine type, status, zone, network interfaces, internal/external IPs, labels, attached disks
Size, type, zone, status, source image, attached instances and labels
Auto/custom subnet mode, routing mode and peerings
CIDR range, region, private Google access and parent VPC
Direction, priority, allowed/denied ports and source ranges — 0.0.0.0/0 exposure is easy to spot
Forwarding rules and backend services with IPs, ports and schemes
Location, storage class, versioning, uniform bucket-level access and labels
Engine and version, tier, region, availability type, IPs and authorized networks, backups and SSL enforcement
Kubernetes version, node pools, location, endpoint and network configuration
Email, display name and disabled state
Which members hold which roles at project level
No agents to deploy. CloudVista uses a read-only service account to discover your Google Cloud estate.
In the Google Cloud console, create a service account in your project, grant it the Viewer role (roles/viewer) and create a JSON key.
Enter the project ID and paste the JSON key on CloudVista's Credentials page. CloudVista validates the connection and starts discovery right away.
Resources appear in the unified inventory alongside your other clouds. Filter by project, region, resource type or label, and export to CSV.
See GCP VPC networks, subnets, VMs and databases on the same interactive topology as your other clouds.
Every sync records what was created, changed or deleted — a timestamped audit trail for incident response and change review.
Monthly Google Cloud costs from the Cloud Billing API, shown beside AWS, Azure and OCI spend.
GCP resources sit in the same searchable inventory as AWS, Azure, OCI, VMware vSphere and GitHub — one filter, one export.
GCP findings — such as disabled service accounts that were never deleted — appear in the same Findings view as your other clouds, with remediation steps.
Add a credential per project and view them together or one at a time. Sync schedules are set per credential.
Create a service account in your Google Cloud project, grant it the read-only Viewer role (roles/viewer), and create a JSON key. Add the project ID and key in CloudVista under Settings, Credentials. CloudVista validates the connection and starts discovering resources across every region and zone in the project.
Compute Engine VM instances, persistent disks, VPC networks, subnets, firewall rules, load balancers, Cloud Storage buckets, Cloud SQL instances, GKE clusters, service accounts and IAM policy bindings.
Yes. Add one service-account credential per GCP project. All projects appear together in the unified inventory, alongside your AWS, Azure, OCI, VMware vSphere and GitHub resources, and you can filter by project or credential.
Yes. If the service account can read the project's billing information through the Cloud Billing API, CloudVista collects monthly GCP costs and shows them with the rest of your multi-cloud spend.
Every connected credential syncs daily by default, and the interval is configurable per credential. You can also trigger a manual sync for a single GCP credential at any time.
Connect a GCP project with a read-only service account and see every VM, cluster, database, bucket and network in minutes. No agents, no credit card.
Start Free Today Live DemoAlso see: Multi-Cloud Inventory · AWS · Azure · OCI · Cloud Inventory Guide · Multi-Cloud Visibility (blog)