FAQ

What is LocalCloud?

LocalCloud is a local Google Cloud development sandbox. It packages a gateway, service facades, external emulator processes, a console, and operator APIs in one Docker container. Each service has explicit operation-level compatibility limits.

Is LocalCloud free?

Yes. During public preview, individuals and organizations, including for-profit companies, may use LocalCloud free of charge for local and internal development, testing, CI, evaluation, and internal pilots. No payment method or license key is required. Read the Licensing page and governing license for the exact terms.

What is the recommended setup?

Install the host CLI, verify Docker, start the selected data-volume runtime, load its generated environment values, and open the returned console URL.

curl -fsSL https://local.cloud/install.sh | sh
localcloud doctor
localcloud start
eval "$(localcloud env)"
localcloud console

The CLI binds to loopback, keeps persistence by default, and can remap occupied ports. Trust the URLs and environment values it returns.

Do I need to change application code?

Some SDKs honor emulator variables without code changes; others require explicit endpoint or client configuration. Load localcloud env into the application process, check the operation matrix, and stop if a client falls back to real Google Cloud.

Which SDK languages are supported?

There is no qualified blanket language matrix. Compatibility depends on client version, transport, endpoint handling, and emulator behavior. Use reviewed examples as a starting point and validate the exact client and operation.

How complete is BigQuery emulation?

BigQuery is a DuckDB-backed local emulator with partial, feature-specific behavior. Exact test totals, function counts, and coverage percentages are not reproducible from a pinned assembled release today. Dependency-sensitive behavior remains release-unverified until source and image provenance are qualified together.

Can I use LocalCloud in CI/CD?

Yes. The Public Preview License permits ongoing internal CI and delivery automation for individuals and organizations, including for-profit companies. Keep local CI credentialless and validate release behavior against real Google Cloud in a separate guarded step.

How much memory does LocalCloud need?

The reviewed CLI default is 4g. Actual use depends on enabled services and workload; no lower-memory guarantee was qualified.

How long does startup take?

There is no maintained cross-platform startup benchmark. Gate automation on localcloud start status plus /health or the workflow-specific readiness endpoint rather than a fixed duration.

Is data persisted between restarts?

The CLI uses persistent storage by default, but persistence is service-specific. Pub/Sub is volatile; other services use different stores and recovery limits. A mounted volume does not provide production durability, replication, or backup semantics.

How do I isolate or reuse a LocalCloud runtime?

The Docker volume mounted at /var/lib/localcloud is durable runtime identity. Use --data-volume NAME on any runtime command for isolated storage. The CLI can attach to a compatible container already using that volume, but it never removes or relabels Docker resources it does not own.

localcloud start --data-volume payments-localcloud-data
localcloud status --data-volume payments-localcloud-data --verbose

Is LocalCloud fully offline?

No categorical offline guarantee applies. Depending on configuration, the runtime can emit telemetry, probe certificate storage, check image updates, validate licenses or live IAM tokens, and dispatch HTTP work. Core local workflows can operate offline after required images are present; review the Privacy and Architecture guides for outbound behavior.

What if a port is already in use?

Use the host CLI so it can remap occupied canonical ports, then reload the generated environment values.

localcloud start
eval "$(localcloud env)"

Do not replace returned endpoint values with a hard-coded port.

What if a service is not responding?

Inspect the selected data-volume runtime and its logs. For manual Docker on canonical ports, /services exposes service state.

localcloud status
localcloud logs --tail 50
curl -fsS http://localhost:24080/services

Confirm the service is enabled, its required tier is available, and its documented support level is suitable for the workflow.

Why do GKE, Compute Engine, or Cloud Run need Docker access?

The host CLI disables Docker-socket access by default. Enable it only for workflows that require subordinate Docker containers or k3d; a read-write socket mount grants broad control of the host Docker daemon.