Stack
Mobile-API Backend
A Postgres + auth + email backend for a native iOS/Android app, with no server to operate.
Why this stack
Supabase is the core: Postgres + Row-Level Security + auth + storage + realtime, all behind a REST/GraphQL API the mobile client can call directly. Vercel (or Cloudflare Workers) hosts any custom edge functions you need beyond what Supabase exposes — webhook receivers, third-party API proxies, push-notification fan-out. Resend handles transactional email (verification, password reset, receipts).
The trade-off vs. Firebase is that you get real Postgres instead of Firestore — joins, transactions, SQL — at the cost of a slightly less polished mobile SDK. The trade-off vs. rolling your own on Fly.io is everything: you skip writing auth, skip writing the API layer, skip ops. For a mobile app where the backend is a means to an end, this is the lowest-overhead path that doesn't lock you into a NoSQL document model.
Build order
Services in this stack
Numbered in the order they should be set up — earlier items are usually dependencies for later ones.
- Top pick
Supabase
Open-source Firebase: Postgres + auth + storage + realtime in one box.
500 MB Postgres, 1 GB storage, 50k MAU, 2 free projects
Database2026-05 - Top pick
Vercel
Next.js-native hosting with edge functions and previews on every push.
100 GB bandwidth/mo, unlimited static sites, 100k edge invocations/day
Hosting2026-05 Cloudflare Workers AI
Run open LLMs on Cloudflare's edge — billed in "Neurons".
10k Neurons/day free, dozens of models including Llama and Stable Diffusion
AI / LLM2026-05- Top pick
Resend
Developer-first transactional email with React Email components.
3k emails/mo, 100/day, 1 verified domain
Email2026-05