GCP

CL4

Connects with a service-account JSON key, validated against the Cloud Resource Manager API with cloud-platform scope. 30+ modular emitters cover VPC, GCE, GKE, Cloud SQL, Cloud Run, and more.

Because cost attribution keys off that literal label, renaming an environment after resources exist breaks the cost link until the label is reconciled — it fails to zero spend, not to a stale number.

Brownfield discovery uses Cloud Asset Inventory's searchAllResources, enriched with the Compute API's aggregated instance list.
Cost attribution depends on a resource-level "environment" label matching the sanitized environment name — a mismatch means zero attributed spend, not an error.

Capability maturity

FinOps (cost sync)
Drift detection
Day-2 operations
Brownfield import
AI copilot

What NebulaStack actually generates for GCP

GCP generation uses 30+ modular edge emitters covering KMS, cache, streaming, data/analytics, compliance, connectivity, FinOps, ML, and backup. Brownfield import reads Cloud Asset Inventory across 25 asset types.

A minimal real resource

resource "google_compute_instance" "web" {
  name         = "web"
  machine_type = "e2-medium"
  zone         = "europe-west1-b"
}

Under the hood

backend/src/services/iac/gcp/**
backend/src/services/gcp/**
backend/src/services/brownfield/gcp/**

Ready to try it?

Start for free, no credit card.

Start for free

Azure

Alibaba Cloud