What is Firebase?
Firebase is Google’s application-development platform, bringing together backend, hosting and app-quality services. The no-cost Spark plan and pay-as-you-go Blaze plan apply at project level, with product-specific access and quotas.
Who is Firebase for?
Mobile and web teams selecting a set of managed app services with a defined project, data and billing arrangement.
Choose the app services, then define the project
Firebase brings together managed app-development services. Its project guide describes a project as the container for registered apps and provisioned resources. A web app and a mobile app registered together should therefore be assessed as one project arrangement, not as isolated subscriptions.
Make a list of the actual services: authentication, application data, uploaded files, hosting and monitoring may have different needs. The individual Cloud Firestore and Authentication profiles describe specific parts of that choice. Compare Supabase as a broader backend option while keeping the data model and operating requirements explicit.
Firebase features
The core capabilities to consider for your workflow.
- Application backend services
- Hosting and development workflows
- Application monitoring and quality tools
Firebase pricing
Spark free plan; Blaze usage pricing
Map the Firebase products used by every app in the project. Compare Spark quotas with Blaze pay-as-you-go access, then review each product’s billing, storage and traffic requirements and any available service-specific cost controls.
Calculate the cost of your quote →Free access & evaluation
Firebase offers the no-cost Spark plan without payment information to get started. Services such as Cloud Storage have separate Blaze requirements; do not assume every product is included in Spark.
Before you choose Firebase
Spark access does not include every Firebase or Google Cloud product.
Linking a Cloud Billing account automatically changes the project to Blaze.
Budget alerts and supported-service spend caps are different controls.
Separate plan access from cost controls
The pricing-plan guide distinguishes Spark from Blaze. The current Cloud Storage FAQ requires Blaze for Storage access; a generic no-cost starting plan should not be read as access to every Firebase product.
The cost-control guidance distinguishes alerts-only budgets from spend caps. The reviewed service caps apply to Firebase AI Logic, App Hosting, Cloud Functions for Firebase and Extensions, and can pause the selected service for the rest of the month. An alerts-only budget does not do that. Check the actual service and control before planning production behaviour.
Explore related software
Firebase FAQs
Do I need payment information or a credit card to start on Firebase Spark?
No. Firebase describes Spark as a no-cost starting plan without payment information. Product-specific access and quotas still apply.
What happens when I link a Cloud Billing account to Firebase?
The project automatically upgrades to the pay-as-you-go Blaze plan. Linking billing is not an app-only change within Spark.
Does Cloud Storage for Firebase require Blaze?
The reviewed Cloud Storage FAQ requires the pay-as-you-go Blaze plan to use Cloud Storage or maintain access to an existing default bucket. No-cost usage allowances do not remove that plan requirement.
Does a Firebase budget alert automatically stop charges?
An alerts-only budget does not pause services or cap charges. Spend cap budgets are separate controls available for specified Firebase services; check their scope and behaviour.
Does the Firebase pricing plan apply separately to each app?
No. The plan applies to the entire Firebase project. Include usage from all apps registered in that project when assessing quotas and costs.