Firebase as a real backend — Firestore modeled with the right indexes and security rules, Cloud Functions v2 with structured logging, and Auth integrated with the rest of the identity story instead of bolted to the side.
Firebase gets dismissed by enterprise architects who haven't shipped on it lately. Cloud Functions v2 (Node 22 + Cloud Run under the hood), App Hosting, and Firestore's modern security rules are a serious backend — for the right shape of workload.
A Firebase backend small teams can move fast on — without painting themselves into a corner when scale demands more.
Concrete deliverables — not adjectives. Each engagement scopes which of these are in play and what success looks like for them.
Drawn from sales calls, not SEO filler. Want a question added? Drop it in the form on this page — we update from real enquiries.
Firebase when the workload is mobile-shaped, realtime-heavy, or already in the Google ecosystem. Supabase when Postgres is the right database. We use both.
Complex relational queries, heavy aggregations, or strict ACID requirements across collections. We migrate to Postgres when those become product requirements.
v2 always for new functions — Node 22, larger memory, Cloud Run runtime. v1 is in maintenance.
Yes — Firebase App Hosting supports Next.js on Cloud Run. We use it where the rest of the stack is Firebase-shaped; otherwise Vercel or self-host.
AWS engineering with the discipline most agencies skip — multi-account landing zones, least-privilege IAM, infrastructure-as-code from the first commit, and FinOps that catches the spend before the CFO does.
Azure engineering for organisations that are Microsoft-shaped — by procurement, by identity (Entra ID / Active Directory), or by line-of-business stack.
GCP engineering — the cloud where data and AI workloads tend to be the deciding factor.
Vercel engineering for teams who want to ship fast and stay shipping fast.
