Runtime details
- Endpoints
- HTTP/REST :24081
- Minimum tier
- community
- Persistence
- service-data
- Documented workflows
- 2
Bucket and object lifecycle workflows for local SDK and API development.
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.
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.
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.
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.
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.
Search text with 3+ characters is sent to PostHog. Do not enter secrets or personal data. Privacy details.
Type to search across all documentation pages
Try: "bigquery", "configuration", "seed data"