Firebase Studio illustrates a concrete choice for software teams: whether the documented integration, authorization and release lifecycle are compatible with the work they want to delegate. This guide distinguishes supported facts from unknown account, region and permission details as of 25 October 2026.
Product and deployment surface
Firebase Studio is a high-impact example of a developer tool whose lifecycle changed during the archive period. Google announced its sunset in March 2026, disabled new workspace creation and signup on June 22, and names March 22, 2027 as the shutdown date for remaining workspaces. Crucially, this is a development-environment transition, not a statement that Cloud Firestore, Firebase Authentication or App Hosting are shutting down.
Worked engineering scenario
An owner should inventory existing Firebase Studio projects now, without assuming deployed apps disappear on the same date. Export source files, note repository commits, identify application hosting, capture environment variables without exposing secrets, list database rules and migrations, and preserve any workspace-specific tool configuration. The migration documentation describes alternate paths through Google AI Studio and Antigravity depending on workflow.
Repository authority and data exposure
After export, rebuild a project outside the retiring environment. Run the exact tests, verify auth redirects and CORS, check whether server environment values were recreated, and validate Firestore or backend policy differences. A migration that reproduces a landing-page screenshot may still lose deployment hooks, cloud functions, scheduled jobs or application data. Keep a rollback plan until the new environment can deploy safely.
Version, licensing and operational limitations
Google’s migration documentation explains that some agent history resides separately from ordinary app files. Teams that need evidence trails or prompt histories should review their workspace and applicable retention rules before deletion. Do not place downloaded environment files or API keys into a public Git repository for convenience.
When the product fits and when to wait
New customers should not be directed to create a Firebase Studio workspace as of the October 2026 cutoff. Existing users should prioritize an inventory and a tested transition before March 2027. The exact service availability and end date are time-sensitive and must be checked again before publication.
Alternatives and selection trade-offs
For a prompt-driven browser app creation experience compare Google AI Studio or Lovable. For code-first local agent work, examine Antigravity, Kiro or a maintained IDE; these alternatives are not one-click replacements for every Studio project.
A reproducible evaluation protocol
- Use a disposable, nonproduction repository at a recorded commit and remove real access tokens, private keys, client information and production data.
- Write acceptance criteria before engaging the assistant: at least one deterministic test, a static check and one failure or rollback scenario.
- Capture the actual tool version, model/provider route, authorized repository, permitted commands and network scope rather than relying on product branding.
- Inspect every changed file and generated dependency. Re-run the build, unit tests and security checks outside the assistant’s self-reported output.
- Separate evidence: vendor documentation, observed measurements from a future controlled trial, and editorial assumptions must have distinct labels.
What was verified—and what was not
The primary evidence for this article is vendor documentation or an original project repository available by the 25 October 2026 editorial cutoff. A product description is evidence of how its publisher represents a capability, not an independent security audit or benchmark. The exact installed build, account entitlement, country, processor, contract and provider model may change the result. We did not install or benchmark the tool for this article.
Availability, licensing and pricing boundary
Snapshot dated 25 October 2026. The verified material here does not provide a complete current price, seat allocation, model quota, region list, retention policy or binding commercial license for each possible tenant. Those entries are deliberately null or unresolved in the structured record. Consult an official account-specific agreement, and link any future numeric plan snapshot to the canonical AI10 pricing registry rather than reproducing a stale marketing offer.
Protect the separately deployed application
Google’s first-party migration guidance distinguishes the Firebase Studio workspace shutdown on 22 March 2027 from core Firebase services, which are not being retired by that change. Preserve source and settings, test the destination deployment and export any agent conversation history that the normal project ZIP does not carry.