Run major GCP services locally
Start one Docker runtime, inspect its local services in the console, and work without a shared cloud development project for every iteration.
Browse the service catalogLocalCloud brings an all-in-one local-development pattern to Google Cloud: service guides, generated local SDK endpoints, and a built-in console. Its proprietary Public Preview License is free for individuals and organizations, including for-profit companies, for non-production development and testing workflows.
LocalStack is designed around AWS service emulation. LocalCloud serves a similar category for Google Cloud APIs under a proprietary Public Preview License. Run local GCP services for development and testing, then validate separately against real Google Cloud.
Swipe horizontally to compare all columns.
| Question | LocalStack | LocalCloud |
|---|---|---|
| Primary cloud | AWS workflows | Google Cloud workflows |
| Google Cloud services | None; LocalStack covers AWS and Snowflake | 25 in one Docker container |
| SDK routing | AWS SDK endpoint overrides | Google Cloud SDK emulator environment variables and endpoint overrides |
| Sign-up and plans | Account and auth token required for current releases since March 23, 2026; free Hobby plan for non-commercial use, paid plans for commercial use | No account or license key; free during the public preview, and free for open-source projects after it |
| Local development goal | Develop and test AWS-connected applications locally | Develop and test GCP-connected applications locally |
| Agent sandbox use | Gives agent-written AWS code a local target | Gives agent-written Google Cloud code a local target with no default credentials or billing project |
| Production validation | Validate against AWS before production | Validate against Google Cloud before production |
LocalStack facts reviewed from LocalStack's site, LocalStack pricing and LocalStack's single-image announcement. See the emulator feature comparisons, including Google's own emulators.
If your application calls AWS APIs, use LocalStack. AWS SDK calls don't reach LocalCloud, and Google Cloud SDK calls don't reach LocalStack, so LocalCloud cannot serve S3, DynamoDB, Lambda, or SQS calls. LocalStack is also the older and more widely deployed project, with a larger community and a wider published integration surface. LocalCloud is the right pick only when the code under test targets Google Cloud — BigQuery, Pub/Sub, Spanner, Bigtable, or Cloud Storage.
Teams building on both clouds commonly run both. The two runtimes bind different local ports and set different SDK environment variables, so they coexist in one development environment.
Start one Docker runtime, inspect its local services in the console, and work without a shared cloud development project for every iteration.
Browse the service catalogPoint local development and test clients at emulator endpoints, then remove the local configuration when exercising real Google Cloud.
See SDK examplesService behavior varies. Review supported capabilities and documented gaps before deciding which tests can stay local.
Review compatibilityYes. LocalCloud is a local Google Cloud runtime for non-production development, testing, CI, evaluation, and internal pilots permitted by its proprietary Public Preview License. It runs major GCP services in Docker so applications can use local endpoints instead of real cloud services.
Not as of October 5, 2026. LocalStack's plans cover AWS and a separate Snowflake product. Since March 23, 2026, current LocalStack releases need a LocalStack account and auth token, and its free Hobby plan is for non-commercial use.
No. LocalCloud is an independent product focused on Google Cloud workflows. LocalStack is an AWS-focused local cloud development platform.
No. LocalCloud is for permitted non-production workflows. Validate behavior against real Google Cloud before production deployment.
LocalCloud is designed for standard Google Cloud SDK and API workflows. Configure local emulator endpoints for development, then remove those local settings when validating against real Google Cloud.
Yes. LocalCloud gives agent-written Google Cloud code a localhost target with no credentials or billing project by default, so an AI coding agent cannot create real cloud resources by mistake. It closes the dependency boundary; pair it with a code sandbox if you also need to contain arbitrary code execution.
The proprietary Public Preview License permits individuals and organizations, including for-profit companies, to use LocalCloud free of charge for internal development, testing, CI, evaluation, and internal pilots. Review the licensing documentation and compatibility details before adopting it for a team workflow.
While analytics is on, search text with 3+ characters is sent to PostHog. Do not enter secrets or personal data. Privacy details.
Type to search across all documentation pages
Try: "bigquery", "configuration", "seed data"