LocalLocalCloud service catalog
Service catalog Find connection details, workflows, and limits for every local service. Services that don't run locally are marked Unsupported. Choose a service for your application task, check its startup requirements, then open its client examples.
25 local services
The ports shown are defaults. Export eval "$(localcloud env)" to use the runtime's actual endpoints. See the service connection reference and capabilities and boundaries as Markdown.
No matching services. Try another service name.
Databases servicesDatabases
Transactional, document, wide-column, relational, and cache workflows.
Firestore
Use when records have evolving fields and fit a collection-and-document model, with reads driven by document IDs or indexed field queries.
ID: firestore · Opt-in: include this ID in the exact enabled-service listFIRESTORE_EMULATOR_HOST
Bigtable
Use when high-volume records can be organized by a row key and retrieved through point lookups or bounded key-range scans. Design the row key around your most frequent reads.
ID: bigtable · Starts by defaultBIGTABLE_EMULATOR_HOST
Spanner
Use when related records need transactional consistency and SQL queries, and your production architecture requires a database that can scale across nodes.
ID: spanner · Starts by defaultSPANNER_EMULATOR_HOST
AlloyDB
Use when an application depends on PostgreSQL SQL, drivers, and transactions, and its production deployment targets AlloyDB. Exercise resource provisioning alongside SQL application tests locally.
ID: alloydb · Starts by defaultALLOYDB_EMULATOR_HOST
Memorystore (Redis/Valkey)
Use when frequently accessed values, expiring entries, counters, or streams fit Redis commands and an in-memory access model. Choose key names and expiries around the application's cache or queue behavior.
ID: memorystore · Starts by defaultREDIS_HOST
Cloud SQL
Use when your application relies on a relational schema, SQL migrations, and transactions through PostgreSQL or MySQL drivers. Test database and user provisioning alongside application queries.
ID: cloudsql · Starts by defaultCLOUD_SQL_EMULATOR_HOST
Messaging & Workflow servicesMessaging & Workflow
Events, jobs, scheduling, and orchestration.
Pub/Sub
Use when several consumers need to react to the same event independently of its publisher. Consumers acknowledge completed work and handle retries without blocking the producer.
ID: pubsub · Starts by defaultPUBSUB_EMULATOR_HOST
Cloud Tasks
Use when a known handler should process queued work with controlled dispatch rates, scheduled delivery, and per-task retry behavior.
ID: cloudtasks · Starts by defaultCLOUD_TASKS_EMULATOR_HOST
Cloud Scheduler
Use when work must recur on a cron schedule in a chosen time zone, with an HTTP endpoint or messaging target receiving each scheduled trigger.
ID: cloudscheduler · Starts by defaultCLOUD_SCHEDULER_EMULATOR_HOST
Cloud Workflows
Use when a process coordinates several API calls and needs explicit sequencing, branching, retries, and a queryable execution result.
ID: workflows · Starts by defaultWORKFLOWS_EMULATOR_HOST
Compute & Runtime servicesCompute & Runtime
Function, container, cluster, VM, and AI control-plane workflows.
Cloud Functions (2nd Gen)
Use when a small handler processes an HTTP request or event and can run as an independently invoked function. Locally, test routing to your own running handler.
ID: cloudfunctions · Starts by defaultCLOUD_FUNCTIONS_EMULATOR_HOST
GKE
Use when deployment depends on Kubernetes manifests and APIs, and you need cluster provisioning plus pod readiness checks. Local tests require Docker and k3d.
ID: gke · Opt-in: include this ID in the exact enabled-service listGKE_EMULATOR_HOST
Compute Engine
Compute Engine doesn't run in LocalCloud; use Google Cloud for VM workloads.
Cloud Run
Use when you can package an HTTP application in a container image and test it through a service URL. LocalCloud runs supported service containers with Docker.
ID: cloudrun · Opt-in: include this ID in the exact enabled-service listCLOUD_RUN_EMULATOR_HOST
Vertex AI
Vertex AI doesn't run in LocalCloud; use Google Cloud for inference and training.
Security servicesSecurity
Secret, identity, and cryptographic API workflows.
Secret Manager
Use when applications retrieve credentials or sensitive configuration at runtime, and values need versioning or rotation independently of an application release.
ID: secretmanager · Starts by defaultSECRET_MANAGER_EMULATOR_HOST
Cloud IAM
Use when resource access depends on which user or service account is making a request, and policies must be managed and tested as part of provisioning.
ID: cloudiam · Starts by defaultIAM_EMULATOR_HOST
Cloud KMS
Use when applications encrypt, decrypt, sign, or verify data using managed keys and explicit key versions. Keep cryptographic key lifecycle separate from application payloads.
ID: kms · Starts by defaultCLOUD_KMS_EMULATOR_HOST
Operations servicesOperations
Projects, service usage, billing metadata, logs, and metrics.
Cloud Resource Manager
Use when automation needs to create, look up, or delete projects and carry their IDs through resource provisioning. Projects provide the scope for the rest of your setup.
ID: cloudresourcemanager · Starts by defaultCLOUD_RESOURCE_MANAGER_EMULATOR_HOST
Service Usage
Use when provisioning clients check API availability or request service enablement before creating resources. Local preflight responses let you exercise those client flows.
ID: serviceusage · Starts by defaultSERVICE_USAGE_EMULATOR_HOST
Cloud Billing
Use when provisioning automation needs to discover a billing account or verify a project's billing association. Local tests exercise the metadata flow with test-owned resources.
ID: cloudbilling · Starts by defaultCLOUD_BILLING_EMULATOR_HOST
Cloud Logging
Use when you need searchable records of individual application events, including severity, structured fields, and request IDs for investigating failures.
ID: logging · Starts by defaultCLOUD_LOGGING_EMULATOR_HOST
Cloud Monitoring
Use when application health is expressed as numeric measurements over time, with labels identifying resources or components. Test metric ingestion and time-window queries with deterministic points.
ID: monitoring · Starts by defaultCLOUD_MONITORING_EMULATOR_HOST
Storage servicesStorage
Buckets, objects, and local file workflows.
Analytics servicesAnalytics
Local data processing, warehouse, and query workflows.
BigQuery
Use when you need to scan datasets, join analytical tables, and calculate aggregates with SQL. Validate reporting queries and transformation outputs against small local fixtures.
ID: bigquery · Starts by defaultBIGQUERY_EMULATOR_HOST
Dataproc
Use when a pipeline uses Spark or Hadoop to transform partitioned datasets, and you need to submit jobs or serverless batches through the Dataproc API.
ID: dataproc · Starts by defaultDATAPROC_EMULATOR_HOST
Auxiliary integration APIsAuxiliary Integration APIs
Data lookup and fixture seeding APIs for other cloud services (e.g. BigQuery external tables); not offered as an individual Google Cloud service.
