# LocalCloud vs Google emulators for agents

> Compare LocalCloud with Google's official emulators for agent workflows on local Google Cloud, with sources and the cases where Google's emulators fit better.
>
> Source: https://local.cloud/compare/google-emulators/

Comparison

Google official emulators are the best source when your target service has one and you want the closest Google-maintained local surface. LocalCloud is the broader agent runtime when one workflow needs many GCP-like services, shared health, seed data, and one container.

[Read docs](https://local.cloud/docs/) [Check compatibility](https://local.cloud/compatibility/) [SDK examples](https://local.cloud/docs/sdk-examples/)

Fact

Google gcloud emulators include service-specific emulator groups.

Fact

LocalCloud runs 25 local services in one Docker image; Firestore is opt-in, and each service documents its local boundaries.

Fact

Neither path removes the need for real-GCP validation before production.

Where Google is better

## Use official emulators for service-specific fidelity

If a single supported official emulator covers your exact service and feature set, it may be the right lowest-risk local dependency. Choose it when:

- It covers the one service and operation you need.
- Following Google's release and compatibility model matters more than a shared multi-service runtime.
- You don't need a shared health check, environment export, seed data, console or cross-service operator routes.

Where LocalCloud is better

## Use LocalCloud for multi-service agent workflows

Count the workflow, not just the services: an agent needs startup, health, environment export, seed data, logs, docs and a clear failure boundary. LocalCloud packages that surface with one start command, one health check and a service catalog that includes services without official Google emulators, such as BigQuery and Cloud Storage. Choose it when:

- One workflow needs several Google Cloud services in one runtime.
- You want one service catalog with operation-level status for every service.
- The CLI's generated endpoints and shared operator routes simplify the local workflow.

Copy-ready setup

## Commands and prompts

### Copy a prompt for your coding agent

#### Start LocalCloud

Give an agent one URL and have it start the local GCP sandbox.

```
Fetch https://local.cloud/ai/agents.md and follow the instructions to start LocalCloud on my machine. Install the LocalCloud CLI if it is missing, verify Docker, start or reuse LocalCloud, export emulator environment variables, and run one local GCP SDK/API smoke check. Do not ask for or use real GCP credentials.
```

#### Configure this repo

Have an agent wire an existing project to LocalCloud safely.

```
Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.
```

Google's emulators: one process per service

```
# Pub/Sub
gcloud components install pubsub-emulator
gcloud beta emulators pubsub start --host-port=localhost:5383

# Firestore
gcloud beta emulators firestore start --host-port=localhost:5384

# Spanner
gcloud components install spanner-emulator
gcloud emulators spanner start --host-port=localhost:5386
```

LocalCloud: one runtime for every service

```
curl -fsSL https://local.cloud/install.sh | sh
localcloud doctor
localcloud start --local-only
curl -fsS http://localhost:5380/readiness
eval "$(localcloud env)"
localcloud console

# Use the endpoint values the CLI returns; it picks another port when a default one is in use.
```

Comparison prompt

```
Compare this repository's GCP usage with LocalCloud service coverage and Google official emulator availability. Recommend the smallest local validation path and list real-GCP checks that must remain.
```

Compatibility

## Local check versus release validation

| Decision point | Google emulators | LocalCloud |
| --- | --- | --- |
| Scope | Individual emulator groups managed through gcloud or service-specific images. | A catalog of operation-specific guides through one LocalCloud runtime entry point. |
| Agent setup | Per-service install, command, ports, and env init. | One Docker image, health endpoint, and shell env export. |
| Best fit | Single-service fidelity where Google ships an emulator. | Multi-service testing, demos, and agent discovery. Individuals and companies can use it free of charge for non-production work during the public preview. |

Production boundary

## Before production

Use LocalCloud for non-production development, testing, and CI under the [Public Preview License](https://local.cloud/license/), check [each service's local boundaries](https://local.cloud/compatibility/), and validate against real Google Cloud before you deploy.

Related

## Next steps

- [GCP emulator overview](https://local.cloud/gcp-emulator/) — LocalCloud positioning against fragmented GCP local development.
- [Compatibility](https://local.cloud/compatibility/) — Current LocalCloud service boundaries.

Sources and review

## Claims are tied to current sources

- [gcloud beta emulators reference](https://docs.cloud.google.com/sdk/gcloud/reference/beta/emulators) — Google emulator command groups.
- LocalCloud agentic facts reviewed 2026-10-20.