Services overview
27 services are listed: 25 run locally; Compute Engine and Vertex AI are cloud-only. Google Sheets is an auxiliary fixture API, not a separate Google Cloud service.
A service guide separates the facts that affect normal use:
- Starts by default — whether
services.enabled: defaultstarts the service. - Minimum tier — Community, or Pro tier, free during preview.
- Status — Supported (ready for local use) or Unsupported (cloud-only).
- Persistence — whether the service keeps its data across restarts.
- Connection — the canonical container port and protocol. Use
localcloud envfor the actual host endpoint. - Known limits — operations or Google Cloud behavior that LocalCloud does not provide.
| Service | Starts by default | Tier | Status | Persistence | Connection |
|---|---|---|---|---|---|
| Firestore | no | Community | Supported | Kept across restarts | gRPC + HTTP/REST :5384 |
| Bigtable | yes | Pro tier, free during preview | Supported | Kept across restarts | gRPC :5385 |
| Spanner | yes | Pro tier, free during preview | Supported | Kept across restarts | gRPC :5386 · HTTP/REST :5387 |
| AlloyDB | yes | Community | Supported | Kept across restarts | gRPC :5380 |
| Memorystore (Redis/Valkey) | yes | Community | Supported | Kept across restarts | RESP :5390 |
| Cloud SQL | yes | Community | Supported | Kept across restarts | HTTP/REST :5380 · PostgreSQL :5391 · MySQL :5406 |
| Pub/Sub | yes | Community | Supported | Kept across restarts | gRPC :5383 |
| Cloud Tasks | yes | Community | Supported | Kept across restarts | gRPC :5380 |
| Cloud Scheduler | yes | Community | Supported | Kept across restarts | gRPC + HTTP/REST :5380 |
| Cloud Workflows | yes | Community | Supported | Kept across restarts | gRPC :5380 |
| Cloud Functions (2nd Gen) | yes | Community | Supported | Resource metadata kept across restarts | gRPC :5380 |
| GKE | no | Pro tier, free during preview | Supported | Resource metadata kept across restarts | gRPC :5380 · k3d :5443 |
| Compute Engine | no | — | Unsupported | Resource metadata kept across restarts | HTTP/REST :5380 |
| Cloud Run | no | Pro tier, free during preview | Supported | Resource metadata kept across restarts | gRPC :5380 |
| Vertex AI | no | — | Unsupported | Resource metadata kept across restarts | HTTP/REST :5380 |
| Secret Manager | yes | Community | Supported | Kept across restarts | gRPC :5380 |
| Cloud IAM | yes | Community | Supported | Resource metadata kept across restarts | gRPC :5380 |
| Cloud KMS | yes | Pro tier, free during preview | Supported | Kept across restarts | gRPC + HTTP/REST :5380 |
| Cloud Resource Manager | yes | Community | Supported | Resource metadata kept across restarts | HTTP/REST :5380 |
| Service Usage | yes | Community | Supported | Resource metadata kept across restarts | HTTP/REST :5380 |
| Cloud Billing | yes | Community | Supported | Resource metadata kept across restarts | HTTP/REST :5380 |
| Cloud Logging | yes | Community | Supported | Kept across restarts | gRPC :5380 |
| Cloud Monitoring | yes | Community | Supported | Kept across restarts | gRPC :5380 |
| Cloud Storage | yes | Community | Supported | Kept across restarts | HTTP/REST :5382 |
| BigQuery | yes | Community | Supported | Kept across restarts | HTTP/REST :5388 · gRPC :5389 |
| Dataproc | yes | Community | Supported | Resource metadata kept across restarts | gRPC :5380 |
| Google Sheets (Auxiliary API) | yes | Community | Supported | Kept across restarts | HTTP/REST :5380 |
Categories
The service catalog groups services by user goal, in this order: Databases, Messaging & Workflow, Compute & Runtime, Security, Operations, Storage, Analytics, and Auxiliary Integration APIs. The table above follows the same order. Implementation boundaries differ inside every category. Some are external emulator processes, some are local facades, and some require Docker-socket or transparent-network opt-ins.
How to use the catalog
- Load the actual running endpoints with
localcloud env; the host CLI may remap ports. - Check the service detail and operation limitations before relying on a workflow.
- Keep the runtime listening only on localhost and use fake local data.
- Remove emulator variables and validate production behavior against real Google Cloud before release.
Open the service catalog for all 27 guides or Compatibility for operation-level support and limitations.
This comment is sent to PostHog. Do not include secrets, personal data, or customer data. See Privacy.