Local request path
Supported requests target loopback endpoints. Review the governing license before use and stop rather than falling back to real Google Cloud.
Complete Guide
How to run Google Cloud services locally
Install the host CLI, start a loopback-bound runtime, and inspect bounded service workflows and limitations.
Why run Google Cloud services locally?
Local emulation provides a controlled inner loop for supported workflows. It does not reproduce production latency, IAM, quotas, or every Google Cloud behavior.
Local feedback loop
Local behavior depends on host resources and is not a production performance benchmark.
Outbound-aware operation
Core workflows can continue after the image is present, but telemetry and other configured features can make outbound requests.
Managed lifecycle
The CLI selects a Docker data volume, manages a loopback-bound runtime, and exports its actual endpoints. Organization use must comply with the proprietary license.
Quick start with the LocalCloud CLI
Install the host CLI, diagnose Docker, start a persistent local runtime, and use its dynamically resolved endpoint settings.
curl -fsSL https://local.cloud/install.sh | sh
localcloud doctor
localcloud start
eval "$(localcloud env)"
localcloud consoleWhat Google Cloud services can run locally?
LocalCloud exposes 27 available services in one managed container. Review each service guide for exact workflows, default enablement, and limitations.
| Service | Port | Local support | Environment Variable |
|---|---|---|---|
| BigQuery | 24087 / 24088 | 10 documented workflows | BIGQUERY_EMULATOR_HOST |
| Cloud Storage | 24081 | 2 documented workflows | STORAGE_EMULATOR_HOST |
| Firestore | 24083 | 2 documented workflows | FIRESTORE_EMULATOR_HOST |
| Pub/Sub | 24082 | 4 documented workflows | PUBSUB_EMULATOR_HOST |
| Spanner | 24085 / 24086 | 5 documented workflows | SPANNER_EMULATOR_HOST |
| Bigtable | 24084 | 13 documented workflows | BIGTABLE_EMULATOR_HOST |
Browse all 27 service guides. Firestore is available but disabled by default; Google Sheets is an available read-only facade with limited A1-range behavior.
Step-by-step setup guide
1
Install Docker
Install Docker Desktop (Mac/Windows) or Docker Engine (Linux). LocalCloud requires Docker to run the emulator container.
2
Install the CLI
Use the checksum-verifying installer on a supported macOS or Linux host:
curl -fsSL https://local.cloud/install.sh | sh3
Diagnose and start
The CLI keeps Docker under your control and starts a loopback-bound persistent runtime:
localcloud doctor
localcloud startUse the URL and endpoint map in the output. If canonical ports are occupied, the CLI assigns dynamic host ports.
4
Configure and inspect
Export the actual local endpoints into the shell that starts your application, then open the selected console URL:
eval "$(localcloud env)"
localcloud console
localcloud statusService-specific setup guides
Each GCP service has unique configuration and SDK patterns. Follow these guides for service-specific setup instructions.
BigQuery
Develop 10 documented DuckDB-backed dataset, table, query, scripting, and API workflows.
Cloud Storage
Use verified bounded bucket and object workflows backed by the LocalCloud volume.
Firestore
Firestore document CRUD and query workflows are available on port 24083. Enable Firestore explicitly before use and review its query, index, seed, and persistence limits.
Pub/Sub
Use partial topic, subscription, publish, pull, and acknowledgement workflows; state is volatile across restart.
Spanner
Use 5 documented Spanner data and administration workflows over gRPC and REST.
Bigtable
Use 13 documented Bigtable data, administration, persistence, and query workflows.
Automating an internal development project
The Public Preview License permits individuals and organizations, including for-profit companies, to use containerized automation for ongoing internal development, testing, and CI.
Keep automation inside the preview boundary
For permitted internal automation, pin the image, wait on /readiness, export values from the running LocalCloud runtime, and stop rather than falling back to real Google Cloud. Customer-facing production use remains outside the preview grant.
See the automation eligibility and integration guide before using a hosted runner.
Frequently asked questions
Why run Google Cloud services locally?
Local emulation can provide a controlled inner loop without sending each supported request to Google Cloud. It does not reproduce production latency, quotas, IAM, or every API behavior.
Do I need to change my application code?
Many bounded workflows use standard Google Cloud clients after localcloud env sets emulator endpoints. Compatibility varies by service and client; never fall back to real Google Cloud silently.
Can I run this in CI/CD pipelines?
Yes. The Public Preview License permits non-production internal CI for individuals and organizations, including for-profit companies. Review the license and test the exact runner before use.
How is LocalCloud licensed?
The proprietary Public Preview License permits individuals and organizations, including for-profit companies, to use LocalCloud free of charge for non-production development, testing, CI, evaluation, and internal pilots. Technical Community or Pro tiers do not expand that legal permission.
Start running GCP services locally
One data-volume runtime, 27 available services, and explicit service boundaries.