| Primary job |
Generate and inspect one API-centric backend contract for an AI-built app: schema, auth, REST endpoints, workflows, docs, and publish state. |
Provide a broad app platform spanning data, auth, serverless logic, hosting, messaging, analytics, monitoring, testing, and AI tooling. |
| Data model |
Relational schemas and relationships are visible in the project graph and exposed through generated REST endpoints. |
Cloud Firestore and Realtime Database provide NoSQL options; SQL Connect adds managed PostgreSQL, GraphQL operations, vector search, and generated typed SDKs. |
| Authentication |
Managed product JWT authentication, password hashing, roles, permissions, and project-defined auth workflows. Configuration still needs project review. |
Firebase Authentication provides mature client SDKs, password, phone, federated providers, and optional Identity Platform features such as MFA, SAML, OIDC, and multi-tenancy. |
| Backend logic |
Visual workflows, functions, tasks, triggers, and supported code-to-visual roundtrips, with REST route testing in API Playground. |
Cloud Functions runs JavaScript, TypeScript, or Python for HTTPS, event, and scheduled workloads; SQL Connect operations and App Hosting cover additional application patterns. |
| Realtime and offline |
Project channels and WebSocket-style runtime features exist; validate the exact channel, authorization, reconnect, and scale behavior required by the app. |
Firestore supplies realtime listeners and offline support, while Realtime Database synchronizes JSON data across connected clients. |
| Coding-agent workflow |
Direct project MCP provides project inspection, build, validation, publish, and review tools. Public-to-project handoff is currently fail-closed. |
Firebase ships an official stdio MCP server in firebase-tools, plus prompts, tools, resources, and agent skills that operate with Firebase CLI credentials. |
| Frontend handoff |
Generates OpenAPI, JSON and Markdown docs, JavaScript and TypeScript SDK output, declarations, snippets, auth notes, and publish-state context. |
Offers mature product SDKs; SQL Connect generates strongly typed app-specific SDKs. Firebase does not center the workflow on one unified REST handoff packet. |
| Hosting and operations |
Hosted project runtimes and per-project static frontend hosting exist, but public SLA, compliance, and generic customer self-host installation are not established. |
Firebase Hosting, App Hosting, Cloud Functions, Crashlytics, Performance Monitoring, Test Lab, Remote Config, and other lifecycle services form a much broader operational platform. |
| Export and migration |
Project, data, and runtime export surfaces exist. That does not prove no lock-in, universal portability, or one-click migration to another platform. |
Firestore supports managed export and import, including full-document exports. Moving an app away still requires replacing Firebase-specific services, SDKs, and rules. |
| Pricing model |
Default developer setup is self-serve through the dashboard, with custom managed builds when requested. Final scope and terms require confirmation. |
Spark provides no-cost access and quotas; Blaze links Cloud Billing and charges pay-as-you-go above product quotas. Costs depend on the services and usage pattern. |
| Maturity and risk |
Earlier-stage product with narrower public trust, support, limits, and production evidence. Use a scoped acceptance test for serious workloads. |
Mature Google-backed platform with a broad ecosystem and production history. Individual architecture, security rules, quotas, and costs still need design and monitoring. |