Borg App Hub replaces Firebase

Build on your own stack.

Give a new app a database, sign-in, and file storage on day one, without standing up servers yourself.

Early access for Search Atlas Mastermind and Enterprise.

The Borg collective Engineering

Supabase
  • No per-seat costNo seat count, no seat price.
  • Unlimited usageNo video, record, or activity caps.
  • Pay only for the AI and compute you useMetered, not per-head.

Workflows to explore

Explore Supabase on Borg

Feature by feature

Supabase: feature coverage

Review Supabase's covered, partly covered and planned features below.

App database

Partly covered

Store and query application data.

Why it matters. An app needs to save and read records.

On Borg. Store and query your app's data in a full PostgreSQL database instead of Firestore's document model.

Authentication

Partly covered

Sign users in and manage identities.

Why it matters. Users need secure access to their own data.

On Borg. Sign users in with Supabase Auth, though the APIs and supported providers differ from Firebase's.

Object storage

Covered

Upload and serve files.

Why it matters. Apps need a place for images and documents.

On Borg. Upload and serve images and documents with access rules attached, the same job Firebase Storage does.

Realtime data

Partly covered

Send data changes to connected clients.

Why it matters. Screens can update without refreshing.

On Borg. Push data changes to connected clients so screens update live, though the behavior differs from Firestore listeners.

Server-side functions

Partly covered

Run backend code in response to app needs.

Why it matters. Some work must run away from the browser.

On Borg. Run backend code with Edge Functions, though self-hosted deployments take extra setup Firebase doesn't require.

Client SDKs

Partly covered

Connect web and mobile apps to backend services.

Why it matters. Developers need tools to read and write data.

On Borg. Connect web and mobile apps with Supabase's SDKs, but expect to rewrite any existing Firebase SDK calls.

Some upstream apps gate certain features behind their own licenses; the coverage chips above say where.

The math

Borg and Firebase: compare the costs

Firebase free Spark tier; Blaze pay as you go

PlanPriceLimits
Spark$0Firestore: 1 GiB stored, 50,000 document reads/day, 20,000 writes/day.
BlazePay as you goEligible no-cost quotas, then usage-based Google Cloud charges.
  • Firestore Standard: 1 GiB storage on Spark.
  • Firestore Standard: 50,000 reads/day and 20,000 writes/day on Spark.
  • Some services require Blaze.

Public pricing checked 2026-10-07. Source

Supabase on Borg App Hub

$0 per seat

  • Unlimited usage, no caps
  • Metered AI + compute, billed to actual use
  • Runs inside a workspace you control

For comparison: Firebase bills for service usage, not team seats; costs depend on reads, writes, storage, and other services.

Questions

Questions about Supabase

Is there an open-source or free alternative to Firebase?

Yes. Supabase is open source and can be self-hosted for free; Appwrite and PocketBase are other open-source options. You pay only for your own infrastructure.

Can I self-host Supabase?

Yes. You must run and maintain its services and storage.

Does Supabase include authentication?

Yes. Supabase Auth offers sign-in, but check your required providers before migrating.

Can Supabase store files?

Yes. Supabase Storage supports file buckets and access policies.

Will Firebase SDK calls keep working?

No. You need to change client code to Supabase APIs.

How does Borg App Hub pricing work?

There's no per-seat cost and no usage caps. You pay only for the AI and compute Supabase uses, as part of your existing Borg subscription.

Weighing options? See the full Firebase alternatives comparison.

Run Supabase without the seat tax.

One App Hub, every tool your team already reaches for. No per-seat cost.

Early access for Search Atlas Mastermind and Enterprise.