App database
Partly coveredStore 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.
Borg App Hub replaces Firebase
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
Workflows to explore
Start an app without running database servers.
Store app data with client SDKs.
Add sign-in and file uploads.
Use a free tier before paying for more usage.
Feature by feature
Review Supabase's covered, partly covered and planned features below.
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.
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.
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.
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.
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.
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
Firebase free Spark tier; Blaze pay as you go
| Plan | Price | Limits |
|---|---|---|
| Spark | $0 | Firestore: 1 GiB stored, 50,000 document reads/day, 20,000 writes/day. |
| Blaze | Pay as you go | Eligible no-cost quotas, then usage-based Google Cloud charges. |
Public pricing checked 2026-10-07. Source
Supabase on Borg App Hub
$0 per seat
For comparison: Firebase bills for service usage, not team seats; costs depend on reads, writes, storage, and other services.
Questions
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.
Yes. You must run and maintain its services and storage.
Yes. Supabase Auth offers sign-in, but check your required providers before migrating.
Yes. Supabase Storage supports file buckets and access policies.
No. You need to change client code to Supabase APIs.
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.
One App Hub, every tool your team already reaches for. No per-seat cost.
Early access for Search Atlas Mastermind and Enterprise.