FAQ

Safety

IAM, network exposure, production use and where data goes.

Can I test IAM permissions with it?

Partly. The IAM API serves custom and predefined roles, service accounts and IAM Conditions, and five named checks read the stored policy: Memorystore for Redis Cluster and Valkey IAM auth, Firestore with MongoDB compatibility sign-ins and command permissions, IAM Credentials on service accounts the IAM API created, BigQuery's per-project IAM for a token the instance minted, and BigQuery remote models' connection permissions. Every other service stores the policy you set and allows each request whatever it says, so a passing local test does not prove your production permissions.

Source: README.md (what will not work), docs/compatibility.md (iam custom roles googleiamadminv1), docs/compatibility.md (credentials metadata and external tooling), docs/gaps.md (excluded on purpose), test/browser/permissions_test.go

Link to this answer

Is it safe to expose on a network?

It binds loopback by default and has no authentication. --allow-remote is required to do otherwise. Don't.

Source: docs/configuration.md (exposure), docs/install.md (safety)

Link to this answer

Should I run production on it?

No. It is for development and testing.

Source: README.md

Link to this answer

Does CloudBurrow send data anywhere?

It exports OpenTelemetry traces only when you set OTEL_EXPORTER_OTLP_ENDPOINT. See docs/configuration.md.

Source: docs/configuration.md (tracing)

Link to this answer

Does it call Google Cloud?

No. Every API is answered on your machine, CloudBurrow never contacts Google to check a token, and the generated credentials grant no Google Cloud access. Two things can still reach the network. Container images, and any local model you choose, are downloaded on first use unless you prefetch them for offline use. And gcloud sends a command for a service with no local override to Google's own endpoint, so keep to the services gcloud-setup configures (the console terminal's gcloud has credentials disabled, so Google refuses such a command there).

Source: docs/adr/0004-local-access-and-no-authentication.md (decision), docs/architecture.md (1 what cloudburrow is), docs/install.md (offline and air gapped use), docs/compatibility.md (console)

Link to this answer
Develop locally

Build against Google Cloud APIs, locally

Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.

Get started