# LocalCloud service catalog > Browse guides for 27 Google Cloud services in LocalCloud: 25 run locally with setup steps, workflows, and code examples; 2 are unsupported. > > Source: https://local.cloud/services/ 25 local services Find connection details, workflows, and limits for every local service. Services that don't run locally are marked Unsupported. Search services [Compatibility](https://local.cloud/compatibility/) The ports shown are defaults. Export `eval "$(localcloud env)"` to use the runtime's actual endpoints. See the [service connection reference](https://local.cloud/ai/services.md) and [capabilities and boundaries](https://local.cloud/ai/compatibility.md) as Markdown. Databases ## Databases services Transactional, document, wide-column, relational, and cache workflows. - [Firestore](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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)](https://local.cloud/services/memorystore/): 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](https://local.cloud/services/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 ## Messaging & Workflow services Events, jobs, scheduling, and orchestration. - [Pub/Sub](https://local.cloud/services/pubsub/): 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](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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 ## Compute & Runtime services Function, container, cluster, VM, and AI control-plane workflows. - [Cloud Functions (2nd Gen)](https://local.cloud/services/cloud-functions/): 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](https://local.cloud/services/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](https://local.cloud/services/compute-engine/): Compute Engine doesn't run in LocalCloud; use Google Cloud for VM workloads. - [Cloud Run](https://local.cloud/services/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](https://local.cloud/services/vertex-ai/): Vertex AI doesn't run in LocalCloud; use Google Cloud for inference and training. Security ## Security services Secret, identity, and cryptographic API workflows. - [Secret Manager](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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 ## Operations services Projects, service usage, billing metadata, logs, and metrics. - [Cloud Resource Manager](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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](https://local.cloud/services/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 ## Storage services Buckets, objects, and local file workflows. - [Cloud Storage](https://local.cloud/services/cloud-storage/): Use when your application stores unstructured files and addresses each object by bucket and name, with uploads, downloads, and object metadata handled through an API. ID: gcs · Starts by defaultSTORAGE_EMULATOR_HOST Analytics ## Analytics services Local data processing, warehouse, and query workflows. - [BigQuery](https://local.cloud/services/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](https://local.cloud/services/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 APIs ## Auxiliary 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. - [Google Sheets](https://local.cloud/services/google-sheets/): Use when an application consumes small, human-maintained lookup tables through A1 ranges. Seed read-only spreadsheet fixtures locally to test how those rows are interpreted. ID: sheets · Starts by defaultSHEETS_EMULATOR_HOST > **Technical availability is not a license grant** > > The governing proprietary license controls permitted use. Review it before personal, employer, organization, commercial, internal-tool, or CI use. Validate production behavior separately against real Google Cloud.