Hosting & Infrastructure - Setup Guide

How to set up Firebase

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Firestore security rules are code-in-a-config. Misconfigured rules leak your entire database publicly. Every Firestore breach story is a missing rule [source: firebase.google.com/docs/rules and multiple public incident writeups on HackerNews].
• Firestore query model does NOT support joins, aggregations, or full-text search natively. You denormalize data or add Algolia/Meilisearch for search.
• Egress bandwidth from Cloud Functions is billed at Google Cloud rates (~$0.12/GB), which surprises apps serving large payloads.
• Firebase Analytics is free but sends data to Google for ad targeting (opt-out available). GDPR concerns apply.
• Realtime Database and Firestore are different products with different pricing and query models. Choosing the wrong one for the use case is a common early mistake.

The 7-step setup

1. 1

   Create your Firebase account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Firebase signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Firebase pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Firebase into the rest of your stack. The integrations that most people set up first: Google Cloud Platform (Firebase runs on GCP), Google Analytics 4, BigQuery (Firestore export for analytics), Slack (Cloud Functions triggers), Stripe (via Cloud Functions), SendGrid, Twilio, all major OAuth providers, iOS and Android SDKs, JavaScript SDK, Flutter, Unity, Genkit (Google's GenAI frame.... Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Firebase deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Firebase - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Firebase for mobile app builders, real-time apps, and MVP teams that want auth + database + storage in one SDK without running a backend. Recommend Supabase when the client wants the same benefits but on Postgres with SQL and open-source. Recommend traditional Postgres (Neon, PlanetScale, AWS RDS) when the client needs relational modeling. Warn about scaling costs on Blaze for high-traffic apps.