2 documented workflows

Run Cloud Storage workflows locally

Bucket and object lifecycle workflows for local SDK and API development.

Runtime details

Endpoints
HTTP/REST :24081
Minimum tier
community
Persistence
service-data
Documented workflows
2

Documented workflows

  • buckets.create/list/delete
  • objects.upload/download/list/delete

Service boundaries

  • [prod_only] IAM, lifecycle policies, and notifications not emulated in LocalCloud.
  • iam, lifecycle policies, notifications: Not supported locally. Production-only control-plane behavior; not applicable to local development.
  • Survives process and container restart while the LocalCloud volume is retained
  • No production durability or replication semantics.
FAQ

Common questions

How do I run Cloud Storage locally?

Install the LocalCloud host CLI, start the runtime, and load the generated environment values into your application process. Cloud Storage is then reachable at the endpoints the CLI reports, and standard Google Cloud clients resolve to localhost instead of googleapis.com.

Which environment variable points the SDK at the local Cloud Storage?

LocalCloud exports STORAGE_EMULATOR_HOST=http://localhost:24081. Read the value from the generated environment rather than assuming a fixed port, because occupied ports are remapped at startup.

What Cloud Storage workflows are documented locally?

2 Cloud Storage workflows are documented with operation-level status: buckets.create/list/delete, objects.upload/download/list/delete. The compatibility matrix lists the status of every operation.

Does the local Cloud Storage behave exactly like Google Cloud?

No. LocalCloud implements documented local workflows with published boundaries, and compatibility is narrower than managed Google Cloud. Validate behavior against real Cloud Storage before production deployment.

Can an AI coding agent use the local Cloud Storage?

Yes. Because no cloud credentials or billing project are required by default, agent-written Cloud Storage code can run against localhost without creating real cloud resources or charges.