Understand App Hosting costs

App Hosting requires a project with the Firebase Blaze pricing plan enabled. This plan has the following no-cost limits for Google Cloud products invoked by App Hosting:

 

Product Feature No-cost Billed
App Hosting Outgoing bandwidth 10 GiB / month $0.15 / cached GiB
$0.20 / uncached GiB
Artifact Registry Storage 0.5 GB / month $0.10 / GB / month for over 0.5 GB
Egress No Cost See Artifact Registry pricing for a full list of egress prices
Cloud Run CPU 180k vCPU-seconds $0.00002400 / vCPU-second
Memory 360k GiB-seconds $0.00000250 / GiB-second
Requests 2M requests $0.40 / million requests
Cloud Build Build-minutes 2500 build-minutes $0.006 / build-minute
Cloud Logging Logging Storage 50 GiB / project / month $0.50/GiB
Logging Retention No cost for 30 days $0.01 / GiB / month for logs retained more than 30 days
Secret Manager Active Secret Versions 6 versions / month $0.06 per version per location
Access Operations 10,000 operations / month $0.03 per 10,000 operations
Rotation Notifications 3 rotations / month $0.05 per rotation

No-cost usage is aggregated across projects by billing account and resets every month; you are billed only for usage past the limits.

Calculate costs

Starting June 14, 2025, you begin incurring costs for your Firebase App Hosting project once you exceed the pay-as-you-go Blaze pricing plan allowances. You will be charged for the following Firebase App Hosting line items:

  • Uncached Outgoing Bandwidth refers to the data transferred directly from the origin servers of the Firebase App Hosting service to fulfill user requests. Origin servers are located between an App Hosting backend's Cloud Run service and Cloud CDN. This occurs when the requested content is not already stored in the Cloud CDN cache (that is, it's uncached). Consequently, the origin server must fetch the data and send it to the user.

    This process incurs costs for two primary reasons:

    1. Populating Cloud CDN caches: When a user requests uncached content, it triggers a process to fetch that data from the origin server and store a copy in the Cloud CDN cache for future requests. This initial transfer of data from the origin to the CDN contributes to the overall cost.
    2. Transferring data to the end user: Once the content is available (either directly from the origin or from the CDN after the initial cache population), it must be transmitted to the end user's device at the requested destination. This data transfer also contributes to the cost.

  • Cached Outgoing Bandwidth refers to the data transferred in gibibytes from Cloud CDN's caches to the end user's device at the requested destination.

See Cache app content for guidance on how to optimize performance with Cloud CDN.

You will also be charged for the usage of the underlying Google Cloud products that your backend uses:

  • Cloud Run
  • Cloud Build
  • Artifact Registry
  • Secret Manager
  • Cloud Logging

The exact price points for these line items can be viewed on our pricing page.