Firebase App Hosting: Setup, Billing and Release Checks
Firebase App Hosting manages a build-and-serving workflow for supported web applications. It is different from renting a VM, and it is a separate product from Firebase Hosting. Choose it for a compatible application rather than because the names sound interchangeable.
This guide follows official documentation reviewed on 18 October 2026. It is not a deployment test. The earlier fixed cost examples, build allowances and no-downtime promises have been removed.
Check framework and product fit
The App Hosting overview describes Cloud Build, Artifact Registry, Cloud Run and Cloud CDN in the managed workflow. Check the current support for your framework version and the features your application uses.
Firebase Hosting is optimised for static and single-page applications and can connect to dynamic services. App Hosting provides an integrated application workflow. Neither choice automatically establishes SEO performance or solves database and authentication design.
1. Prepare a test project and a cost estimate
Follow the getting-started guide. App Hosting requires the pay-as-you-go Blaze plan. Review its billing implications before enabling it, and use a non-production project for the first trial.
The cost documentation covers App Hosting transfer and underlying resources such as builds, serving, artifacts, secrets and logs. No-cost allowances are limits within the pricing model, not a promise that the whole project stays free. Add separately used databases and other services to the estimate.
2. Create a backend and connect the intended code
In Firebase’s App Hosting workflow, create the backend and select a supported location. If using the documented GitHub route, authorise only the intended repository and choose the live branch and app root carefully.
Keep production credentials out of the trial. Review which commits trigger automatic rollouts so an ordinary push does not unexpectedly publish unfinished work.
3. Configure runtime and secrets
Use the current backend configuration guide for apphosting.yaml, instance settings and environment availability. Plain environment values and secret references have different purposes. Do not commit private keys or expose secrets through browser-delivered code.
Minimum and maximum instances, concurrency, CPU and memory affect behaviour and cost. Choose tested settings rather than copying a sample unchanged. Scaling has limits; it does not guarantee that an application or its database survives every traffic spike.
4. Inspect the rollout and application
Review build and runtime logs, then use the generated backend URL. Test server-rendered routes, static assets, authentication, database access and error handling. Verify a fresh session and an uncached request as well as the homepage.
Monitor the project’s actual resource usage. Billing notifications need an owner; a notification alone is not an enforced spending ceiling.
5. Practise release recovery
The rollout documentation distinguishes restoring an existing build from rebuilding an earlier commit. Configuration and secrets can differ between those paths. Rolling back application code is not the same as undoing database changes.
Keep the backup and restore plan separate, and use the application performance method for acceptance evidence. Connect a production domain only after the application, recovery procedure and operating budget pass your checks.



