Glossary

Cloud emulator

A local program that implements a cloud provider's service APIs so application code can be developed and tested without calling the managed cloud. Distinct from a cloud-hosted device emulator, which runs a mobile operating system on remote hardware.

Fact

In this documentation, cloud emulator always means an emulator of cloud service APIs.

Fact

Emulators trade managed-cloud fidelity for speed, isolation, and zero cloud cost.

Fact

Every emulator has documented gaps; production behavior is validated against the real provider.

Definition

What Cloud emulator means here

A local program that implements a cloud provider's service APIs so application code can be developed and tested without calling the managed cloud. Distinct from a cloud-hosted device emulator, which runs a mobile operating system on remote hardware.

  • In this documentation, cloud emulator always means an emulator of cloud service APIs.
  • Emulators trade managed-cloud fidelity for speed, isolation, and zero cloud cost.
  • Every emulator has documented gaps; production behavior is validated against the real provider.
LocalCloud boundary

How to use the term safely

In LocalCloud content, this term should not imply production replacement, legal permission, hidden credentials, or complete cloud parity. It describes a bounded local-development workflow that still needs license review and release validation against real Google Cloud.

Limitations

Use the sandbox deliberately

  • Permitted workflows use local endpoint values and should stop rather than fall back to real Google Cloud or real credentials. The Public Preview License permits individuals and organizations, including for-profit companies, to use LocalCloud for non-production internal development, testing, CI, evaluation, and pilots.
  • LocalCloud emulates bounded local development workflows. Validate application behavior against real Google Cloud before production deployment.
  • Before production deployment, unset LocalCloud emulator environment variables and validate behavior against real Google Cloud.
Next routes

Keep the agent on the supported path