Services overview

The runtime includes 27 service entries and publishes 27 guides. 25 entries have documented local integration workflows; unsupported and unknown entries remain in the catalog for reference. Google Sheets is an auxiliary fixture API, not a separate Google Cloud service. Availability does not mean full Google Cloud parity or that a service starts by default.

A service guide separates the facts that affect normal use:

1. Starts by default — whether services.enabled: default starts the service.
2. Minimum tier — Community, or Pro tier, free during preview. The tier is a technical setting in the runtime; the license governs use.
3. Status — Supported (ready for local use) or Unsupported (cloud-only).
4. Persistence — whether data is volatile, metadata-only, service data, or stateless.
5. Connection — the canonical container port and protocol. Use localcloud env for the actual host endpoint.
6. Known limits — operations or Google Cloud behavior that LocalCloud does not provide.

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.