App backend

Firebase

Use managed app services, including authentication and Firestore document data.

Sources checked 4 Oct 2026

Our recommendation

When to choose it

Choose Firebase when its document model and mobile integrations match how your app works. Learn Security Rules before exposing data.

Start with Supabase instead when relationships, SQL and relational reporting are central.

Firestore documents are a different data model from relational tables and joins.
Write and test Security Rules; a signed-in user should not automatically access every document.

Product-specific plans and pay-as-you-go usage

Reads, writes, storage and other products have separate billing boundaries. Review each product you enable.

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.