The open-source Firebase for Cloudflare.
Ship auth, realtime data, and SQL from your own Cloudflare account - global by default, zero servers to run, no egress bill. Open source, and yours to keep.
POST /db/collections/posts/documents · GET /auth/token · it's just HTTP
Built natively on the Cloudflare Developer Platform
A backend in one command.
Scaffold a Worker with auth installed, add the database, deploy to your own Cloudflare account.
$ npx @frostbase-dev/cli init my-backend Or let your agent do it
Paste this into any coding agent.
> Read frostbase.dev/agents.md and set up Frostbase in this project agents.md includes a zero-account path: the agent builds on a throwaway demo project and hands you the live dashboard.
Our price: $0
Frostbase is open source and runs on your own Cloudflare account - there is no middleman bill, and Durable Objects sit on the Workers free tier, so small projects run at $0. This estimates what a workload costs on your account, next to the same app on Firebase and Supabase.
Frostbase on your Cloudflare account
- Workers Paid base $5.00
- Requests & compute $34.05
- Database rows $0.00
- Storage $39.00
Rows read are effectively free: 25 billion are included before the first $0.001/M. Realtime pushes bill as Durable Object requests at $0.15/M.
The same app on Firebase (Firestore, nam5)
59× the Cloudflare bill
- Document reads (incl. 150M listener reads) $101.10
- Document writes $16.92
- Storage $35.82
- Auth MAU (free to 50k) $4,415
The structural difference: Firestore bills every document a realtime listener receives as a read ($0.06 per 100k) - fan-out multiplies the bill by subscriber count. Free tier (50k reads / 20k writes per day) is folded in; auth past 50k MAU uses Identity Platform's graduated rates.
The same app on Supabase (Pro)
- Pro base (incl. one Micro instance) $25.00
- Auth MAU (free to 100k) $2,925
- Database storage $24.00
- Realtime $1,358
Reads and writes are not metered per operation on Supabase - sustained load is provisioned compute (bigger instances), which this estimate leaves out, in Supabase's favor. Realtime bills peak connections ($10 per 1000 past 500) and messages ($2.50/M past 5M).
Model assumptions and sources
An estimate whose assumptions are hidden is an ad, not a tool. This one assumes: each API read or write is one Worker request plus one Durable Object request (~3ms CPU, ~5ms DO time); a read touches ~4 SQLite rows and a write ~3; each realtime connection receives ~50 pushed updates a day; daily free-tier allowances are folded to months assuming steady traffic. Idle WebSockets hibernate and cost nothing while quiet. MAU is an auth headcount only - Frostbase has no per-user charge (auth requests are ordinary requests), while Firebase and Supabase bill MAU directly past their free allowances. Supabase's compute sizing, egress, Workers AI (the copilot), and multi-region read replicas are not modeled.
Rates as of 2026-08-06, from Cloudflare Workers pricing, Durable Objects pricing, Cloud Firestore pricing, Firebase pricing, Identity Platform pricing, Supabase pricing. All three bills are estimates - measure before you commit either way.
Same primitives. Different physics.
Firebase's DX, Supabase's openness, Cloudflare's network. Every row is a reason this exists.
| Capability | Firebase | Supabase | |
|---|---|---|---|
| Authentication | Better Auth in a per-project agent | Firebase Auth | Supabase Auth |
| Documents with live queries | a Durable Object per collection | Firestore | JSONB columns + realtime channels |
| Typed SQL tables | ORM-ready schema, gated raw SQL | documents only | Postgres |
| Branching | the whole backend - auth included - free | clone the project by hand | database only, paid |
| Read replicas near users | on by default, per collection | region fixed at create | paid add-on |
| Point-in-time restore | 30 days, built in | paid, up to 7 days | paid add-on |
| Egress fees | $0 bandwidth | metered per GB | metered past the cap |
| Compliance | your Cloudflare account's certs - no new data processor | Google's certs, but another processor to review | SOC 2 gated to the paid Team plan, HIPAA an add-on |
| Open source + self-hosting | Apache-2.0, deploys to your account | proprietary | their cloud or yours |
Competitor capabilities as publicly documented; exact prices with dated sources live on the pricing page.
It's just HTTP. SDKs optional.
Point fetch at your project's endpoint and you're
integrated - this is the exact API the demo dashboard uses. When you want types, the
Better Auth client and @frostbase-dev/db/client wrap the same
routes.
- Cookie sessions for same-origin browser apps
- Bearer tokens via the
set-auth-tokenheader for external and non-browser clients - Per-project trusted origins - add yours under Authentication → Settings
- Public config endpoint:
GET /api/projects/:projectId/config
// Create a post (public collection: no token needed)
await fetch('/api/projects/PROJECT_ID/db/collections/posts/documents', {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify({ data: { title: 'Show HN: my launch', votes: 1 } })
});
// The front page: top 25 by votes
const { docs } = await (await fetch('/api/projects/PROJECT_ID/db/collections/posts/query', {
method: 'POST',
headers: { 'content-type': 'application/json' },
body: JSON.stringify({ orderBy: [{ field: 'votes', direction: 'desc' }], limit: 25 })
})).json();Three Workers. A Durable Object per primitive.
That's the whole diagram. No origin fleet, no connection pools - your backend state lives with the compute that serves it.
Enter at the edge
Requests hit Cloudflare's network and the same-origin gateway, which preserves your cookies, origin, and the edge-resolved country before routing over a service binding.
One agent per primitive
Auth lives in your project's AuthAgent Durable Object; every database collection gets a Durable Object of its own - embedded SQLite, strongly consistent, no connection pool, no separate database to run.
Fan out in realtime
State changes sync to connected dashboards over WebSockets, and auth events stream to Workers Analytics Engine for the charts.
Every Firebase primitive. All of them shipped.
We shipped them one at a time, and every one landed the same way: its own agent, one Durable Object per client project, and a same-origin dashboard proxy.
Auth
LiveDatabase
LiveStorage
LiveRealtime
LiveQuestions, answered plainly.
Spin up a real Durable Object in one click.
Opening the dashboard creates an isolated demo project for your browser. Poke the API, watch the state sync live, ask the copilot about it.