LocalCloud AlloyDB Local Emulator
Get started
local.cloud — AlloyDB Local Emulator .md Open tab
LocalCloud Google Cloud in-a-box

AlloyDB

AlloyDB is Google Cloud’s PostgreSQL-compatible database service. LocalCloud combines AlloyDB resource metadata with a local PostgreSQL connection for application tests.

When to use AlloyDB

Typical uses

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.

Examples

  • PostgreSQL application backends
  • Database provisioning and connection tests
Databases

Explore another service

View all
Local workflow

Example usage

Install the CLI, start LocalCloud, and export its environment in the same shell. Generated endpoints account for remapped ports.

1. Install and start · shell
curl -fsSL https://local.cloud/install.sh | sh
localcloud start --local-only
# Export GOOGLE_CLOUD_PROJECT and ALLOYDB_EMULATOR_HOST
eval "$(localcloud env)"

Provision metadata and query PostgreSQL

  1. Create local cluster and instance metadata.
  2. Connect the application to the documented PostgreSQL endpoint.
  3. Create a table, insert a fixture, and query it back.

Documented workflows

  • Cluster/instance CRUD and local PostgreSQL access
  • Configuration patching, flag discovery, and backup metadata restore

Service boundaries

  • Backup restore covers metadata
  • No advanced AlloyDB engine behavior or replicas
  • Managed regional failover is cloud-only
Try it in your project

Code examples and integrations

Start with the local guides. Official Google Cloud samples may need endpoint changes and can cover features outside the workflows listed here.

Integration

Build an integration test loop

Start the runtime, verify readiness, exercise your SDK, and clean up test state.

Open guide
Agent testing

Use AlloyDB with an AI agent

Before the agent changes application logic, have it create local AlloyDB state, read it back with the project SDK, and note which feature the check covered. That first local call catches accidental production routing and needs no GCP account, service-account key, or billing project.

Configure this repo

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Production endpoints, auth, IAM, quotas, regional behavior, and final release validation still need the target Google Cloud project.

Agent resources has more prompts and the AGENTS.md template.

Related guides

Desktop view