App backend

Supabase

Combine PostgreSQL, authentication, file storage and realtime features in one backend.

Sources checked 4 Oct 2026

Our recommendation

When to choose it

Start with Supabase when your app needs relational data and you want authentication and storage beside it.

Prefer Firebase when a document-oriented mobile workflow is the deliberate architecture choice.

Authentication identifies a user; row-level security still decides which rows they may access.
Keep privileged secret keys on the server. A public client key does not replace ownership policies.

Project plans, compute and additional usage

Budget per project and review database, storage and transfer usage. Check recovery features for the chosen plan.

This is a pricing model, not a monthly quote. Check your region, intended usage and current plan before buying.

These are technical connections you can configure. Selecting a card creates no accounts or resources.

Lessons open through your account and the kits you own.

Feature sources were reviewed on 4 Oct 2026. Plans and availability can change.