Grouped the way Google Cloud teams already scan the platform.
Databases services for local development.
Transactional, document, wide-column, and cache-style data services for app backends.
Firestore
Document database for app state, user data, and event-driven backends.
Spanner
Relational database surface for strongly consistent SQL and transactional workloads.
Bigtable
Wide-column store for large key ranges, event streams, and time-series workloads.
Memorystore
Redis-compatible cache and low-latency data surface for local development.
Cloud SQL
Managed relational database service for local Cloud SQL API workflow testing.
Messaging & Workflow services for local development.
Events, background jobs, and orchestration surfaces for distributed application flows.
Pub/Sub
Messaging and event streaming for async, fan-out, and queue-driven flows.
Cloud Tasks
Managed task queue behavior for background jobs and HTTP dispatch workflows.
Cloud Workflows
Workflow orchestration for multi-step service calls and long-running flows.
Compute & Runtime services for local development.
Container, cluster, and instance-style runtime surfaces when app flows need them.
GKE
Cluster-oriented runtime surface for Kubernetes-style local testing.
Compute Engine
VM-like runtime surface for instance-based local workflows.
Cloud Run
Serverless container runtime behavior for local service deployment flows.
Vertex AI
AI/ML platform service for local model training, prediction, and Vertex AI workflow testing.
Security services for local development.
Secret and configuration access patterns developers need during local iteration.
Operations services for local development.
Logs, metrics, and operational visibility surfaces that help teams trust local runs.
Storage services for local development.
Buckets, blobs, and object access patterns for local file-heavy workflows.
Analytics services for local development.
Warehouse-style SQL and dataset workflows for local query development.
LocalCloud provides health & usage for each service via in-built console app.
Pull the image, start the container, export the env block, and begin testing locally.
Compute-oriented surfaces stay clearly marked when Docker-backed behavior is required.