A cloud instance is a space's own Firebase project. Once it is connected, every project created in the space keeps its data there — Firestore, Realtime Database and Storage — instead of in the shared platform cloud. The data is yours, in a Google Cloud project you own and pay for; the platform holds only a credential to it and runs the same API, console and hosting on top.
What moves and what stays#
| Lives in your cloud | Stays with the platform |
|---|---|
| Every project's data: documents, products, orders, customers, invoices, files, schemas, templates, settings | The project's root record (its name, space and the binding to your cloud) |
| The project's credits, coupons and codes | Access tokens and identity tokens |
| Stock ledgers and payment records of your projects | The credits wallet and the plan (billing never depends on data you can edit) |
| Uploaded files (the default Storage bucket) | Paid AI usage logs, traffic statistics |
The API, the SDK, MCP and the tenant hosting work exactly as for any project — a request is routed to your cloud behind the scenes. If your cloud stops answering (a revoked key, a deleted project), its projects answer 503 org_unreachable until access is restored; tokens, the wallet and the plan are untouched.
Who can use it#
- The space needs the Enterprise plan on at least one of its projects.
- Only the space owner connects, re-checks, updates or disconnects the cloud; admins and members see it read-only.
- A cloud is bound per environment: Production and Demo are two clouds (Environments).
How it works, in one paragraph#
You upload a service-account key of your Firebase project. The platform checks what the key can do, creates whatever the project lacks (the Firestore database, the Realtime Database, the Storage bucket) in the location you chose, adds the indexes the platform needs, and deploys a small forwarder — the shim — into your project, so writes there reach the platform's logic (order status, stock, hooks, slugs). From then on, new projects in the space are created in your cloud. See Connecting, What gets set up and The shim.
Not available yet#
Moving an existing project into a cloud (a project is placed at creation), connecting through an IAM grant instead of a key, a project hosted by the platform on request, and one-click creation of the Firebase project itself.