$0
No-cost plan for supported services and a limited SQL Connect trial.
- No payment method required
- Cloud Storage, Cloud Functions and App Hosting require Blaze
- SQL Connect offers one time-limited Cloud SQL trial instance per project
Managed backend services for web and mobile applications.
Web and mobile teams that want to build client-facing apps without assembling their own authentication, database APIs and hosting infrastructure.
Moving away can require replacing Firebase-specific client APIs, security rules and integrations, even when the underlying database is PostgreSQL.
Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.
Published pricing structure, representative costs, and material billing factors.
Project-level plans. Individual services have different allowances, eligibility and meters.
$0
No-cost plan for supported services and a limited SQL Connect trial.
Usage-based
Pay-as-you-go plan with a linked Cloud Billing account.
Representative Blaze meters; rates, allowances and units differ by service, region and configuration.
| Resource | Billing Unit | Price |
|---|---|---|
| SQL Connect client operations | per million above 250,000 per month | $0.90 |
| Hosting transfer | per GB after 360 MB per day | $0.15 |
| Realtime Database downloads | per GB after 360 MB per day | $1 |
| Realtime Database storage | per GB after 1 GB | $5 |
| Phone authentication | per verification SMS | Varies by destination |
Selected recurring allowances. Spark requires no payment method; Blaze requires a linked billing account even when usage stays within an allowance.
SQL Connect offers a 90-day Cloud SQL trial. Spark permits one trial instance per project; without upgrading it is archived at expiry and deleted 90 days later. Blaze trials require the default instance configuration, are limited per project and billing account, and configuration changes can end the trial early. Other charges can apply.
Spark is no-cost within product limits. Blaze charges applicable usage and separately billed Google Cloud resources.
Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.
Firebase services have distinct placement, regional execution and delivery footprints. Counts refer only to the named footprint.
Regional database location; replicated across zones in the selected region. Default database placement can share a legacy location dependency.
| Location | Region ID |
|---|---|
North America
11 regions
| |
| Oregon | us-west1 |
| Los Angeles | us-west2 |
| Salt Lake City | us-west3 |
| Las Vegas | us-west4 |
| Iowa | us-central1 |
| Montréal | northamerica-northeast1 |
| Toronto | northamerica-northeast2 |
| South Carolina | us-east1 |
| Northern Virginia | us-east4 |
| Columbus | us-east5 |
| Dallas | us-south1 |
Latin America
3 regions
| |
| Queretaro | northamerica-south1 |
| Santiago | southamerica-west1 |
| São Paulo | southamerica-east1 |
Europe
13 regions
| |
| London | europe-west2 |
| Belgium | europe-west1 |
| Netherlands | europe-west4 |
| Milan | europe-west8 |
| Madrid | europe-southwest1 |
| Paris | europe-west9 |
| Turin | europe-west12 |
| Berlin | europe-west10 |
| Frankfurt | europe-west3 |
| Finland | europe-north1 |
| Stockholm | europe-north2 |
| Warsaw | europe-central2 |
| Zürich | europe-west6 |
Middle East & Africa
4 regions
| |
| Doha | me-central1 |
| Dammam | me-central2 |
| Tel Aviv | me-west1 |
| Johannesburg | africa-south1 |
Asia Pacific
12 regions
| |
| Mumbai | asia-south1 |
| Delhi | asia-south2 |
| Singapore | asia-southeast1 |
| Jakarta | asia-southeast2 |
| Bangkok | asia-southeast3 |
| Hong Kong | asia-east2 |
| Taiwan | asia-east1 |
| Tokyo | asia-northeast1 |
| Osaka | asia-northeast2 |
| Seoul | asia-northeast3 |
| Sydney | australia-southeast1 |
| Melbourne | australia-southeast2 |
Each selectable multi-region location contains read-write replicas and a witness across documented regions. These are database locations, not Functions execution regions.
| Location | Area | Location ID |
|---|---|---|
| Europe Read-write Belgium and Netherlands; witness Finland. | Europe | eur3 |
| United States (Central) Read-write Iowa and private Oklahoma; witness South Carolina. | North America | nam5 |
| United States (Central and East) Read-write Iowa and Northern Virginia; witness private Oklahoma. | North America | nam7 |
Customer selects a database region independently of Firestore and Storage.
| Location | Area | Region ID |
|---|---|---|
| Iowa | North America | us-central1 |
| Belgium | Europe | europe-west1 |
| Singapore | Asia Pacific | asia-southeast1 |
Region selection and pricing tier depend on generation. Hong Kong and London occur in both pricing tables, with different generation support.
| Location | Region ID |
|---|---|
Middle East & Africa
4 regions
| |
| Johannesburg Tier 1; 2nd generation only. | africa-south1 |
| Tel Aviv Tier 1; 2nd generation only. | me-west1 |
| Doha Tier 2; 2nd generation only. | me-central1 |
| Dammam Tier 2; 2nd generation only. | me-central2 |
Asia Pacific
11 regions
| |
| Taiwan Tier 1; 1st and 2nd generation. | asia-east1 |
| Hong Kong Tier 1: 1st generation; Tier 2: 2nd generation. | asia-east2 |
| Tokyo Tier 1; 1st and 2nd generation. | asia-northeast1 |
| Osaka Tier 1; 1st and 2nd generation. | asia-northeast2 |
| Seoul Tier 2; 1st and 2nd generation. | asia-northeast3 |
| Singapore Tier 2; 1st and 2nd generation. | asia-southeast1 |
| Jakarta Tier 2; 1st and 2nd generation. | asia-southeast2 |
| Mumbai Tier 2; 2nd generation only. | asia-south1 |
| Delhi Tier 2; 2nd generation only. | asia-south2 |
| Sydney Tier 2; 1st and 2nd generation. | australia-southeast1 |
| Melbourne Tier 2; 2nd generation only. | australia-southeast2 |
Europe
12 regions
| |
| Finland Tier 1; 2nd generation only. | europe-north1 |
| Madrid Tier 1; 2nd generation only. | europe-southwest1 |
| Belgium Tier 1; 1st and 2nd generation. | europe-west1 |
| Netherlands Tier 1; 2nd generation only. | europe-west4 |
| Milan Tier 1; 2nd generation only. | europe-west8 |
| Paris Tier 1; 2nd generation only. | europe-west9 |
| London Tier 1: 1st generation; Tier 2: 2nd generation. | europe-west2 |
| Warsaw Tier 2; 1st and 2nd generation. | europe-central2 |
| Frankfurt Tier 2; 1st and 2nd generation. | europe-west3 |
| Zürich Tier 2; 1st and 2nd generation. | europe-west6 |
| Berlin Tier 2; 2nd generation only. | europe-west10 |
| Turin Tier 2; 2nd generation only. | europe-west12 |
North America
11 regions
| |
| Iowa Tier 1; 1st and 2nd generation. | us-central1 |
| South Carolina Tier 1; 1st and 2nd generation. | us-east1 |
| Northern Virginia Tier 1; 1st and 2nd generation. | us-east4 |
| Columbus Tier 1; 2nd generation only. | us-east5 |
| Dallas Tier 1; 2nd generation only. | us-south1 |
| Oregon Tier 1; 1st and 2nd generation. | us-west1 |
| Montréal Tier 2; 1st and 2nd generation. | northamerica-northeast1 |
| Toronto Tier 2; 2nd generation only. | northamerica-northeast2 |
| Los Angeles Tier 2; 1st and 2nd generation. | us-west2 |
| Salt Lake City Tier 2; 1st and 2nd generation. | us-west3 |
| Las Vegas Tier 2; 1st and 2nd generation. | us-west4 |
Latin America
2 regions
| |
| São Paulo Tier 2; 1st and 2nd generation. | southamerica-east1 |
| Santiago Tier 2; 2nd generation only. | southamerica-west1 |
SQL Connect and its associated Cloud SQL PostgreSQL instance must use the same region. Spark trials are not offered in Singapore or Jakarta.
| Location | Region ID |
|---|---|
Asia Pacific
10 regions
| |
| Taiwan | asia-east1 |
| Hong Kong | asia-east2 |
| Tokyo | asia-northeast1 |
| Osaka | asia-northeast2 |
| Seoul | asia-northeast3 |
| Mumbai | asia-south1 |
| Singapore Unavailable for Spark trials. | asia-southeast1 |
| Jakarta Unavailable for Spark trials. | asia-southeast2 |
| Sydney | australia-southeast1 |
| Melbourne | australia-southeast2 |
Europe
10 regions
| |
| Warsaw | europe-central2 |
| Finland | europe-north1 |
| Madrid | europe-southwest1 |
| Belgium | europe-west1 |
| London | europe-west2 |
| Frankfurt | europe-west3 |
| Netherlands | europe-west4 |
| Zürich | europe-west6 |
| Milan | europe-west8 |
| Paris | europe-west9 |
Middle East & Africa
1 region
| |
| Tel Aviv | me-west1 |
North America
10 regions
| |
| Montréal | northamerica-northeast1 |
| Toronto | northamerica-northeast2 |
| Iowa | us-central1 |
| South Carolina | us-east1 |
| Northern Virginia | us-east4 |
| Dallas | us-south1 |
| Oregon | us-west1 |
| Los Angeles | us-west2 |
| Salt Lake City | us-west3 |
| Las Vegas | us-west4 |
Latin America
2 regions
| |
| São Paulo | southamerica-east1 |
| Santiago | southamerica-west1 |
New default and additional buckets use supported Cloud Storage locations, excluding configurable dual-regions. Legacy appspot.com defaults use App Engine locations and location dependency. Locations and Always Free eligibility vary.
A backend runs in its chosen primary region; uncached content is served there while the CDN delivers cached content globally.
| Location | Area | Region ID |
|---|---|---|
| Iowa | North America | us-central1 |
| Northern Virginia | North America | us-east4 |
| Columbus | North America | us-east5 |
| Taiwan | Asia Pacific | asia-east1 |
| Singapore | Asia Pacific | asia-southeast1 |
| Netherlands | Europe | europe-west4 |
Hosting delivers static content using a global CDN. A stable Firebase-specific PoP inventory or count was not established; delivery is not Functions execution.
Availability reviewed
60 minutes
Second generation; callable client timeouts can be shorter
9 minutes
Second generation; scheduled and task queue functions have a separate 30-minute maximum
Up to 32 GiB
Second generation; regional quotas also apply
100 on Spark; 200,000 per database on Blaze
Simultaneous connections; Blaze supports multiple databases