Stop guessing which one. Put them side by side.

The grid says what these tools are. This says what builders did about it — one decision per person, changeable whenever you change your mind.

# Tool comparison — Firebase vs Drizzle ORM vs PocketBase

Source: Kbaise, a directory of tools that work with Lovable projects.
Pick one and tell me why before writing any integration code.

## Firebase (firebase)
- URL: https://firebase.google.com
- Category: Databases & backend
- Cost: mixed — Spark free: Firestore 1GiB, 50K reads/20K writes per day, 10GiB egress, 50K Auth MAU. Blaze is pay-as-you-go; Cloud Functions require Blaze.
- What it is: Google's backend suite: Firestore and Realtime Database, Authentication, Hosting, Cloud Functions and Cloud Messaging. The no-cost Spark plan gives 1GiB Firestore storage with 50,000 reads and 20,000 writes per day. Blaze is pay-as-you-go and is required for Cloud Functions and outbound networking.
- Why builders pick it: Fifteen years of tutorials means models generate Firebase code confidently. An official MCP server ships inside firebase-tools, and Firebase Studio is Google's own AI app builder wired straight into it.
- Trap: Per-document read billing punishes chatty UIs, and a runaway loop on Blaze can produce a shocking bill overnight. NoSQL modelling also resists later migration to SQL.
- Wiring: npx -y firebase-tools@latest mcp
- Full dossier: /api/public/tools/firebase

## Drizzle ORM (drizzle-orm)
- URL: https://orm.drizzle.team
- Category: Databases & backend
- Cost: free — Free and open source under Apache 2.0. Drizzle Studio and Drizzle Kit are free; Drizzle Gateway is in closed alpha.
- What it is: A headless TypeScript ORM whose query API deliberately mirrors SQL, so a Drizzle query reads like the statement it compiles to. Supports Postgres, MySQL, SQLite, SingleStore, MSSQL and CockroachDB, with dedicated drivers for Neon, Supabase, Turso, PlanetScale and Cloudflare D1. Drizzle Kit handles migrations.
- Why builders pick it: No code generation step and no separate engine binary, so it runs inside edge runtimes and whatever sandbox an agent is building in. Being close to SQL, models translate a schema idea into working queries with fewer invented helpers.
- Trap: Relational query ergonomics are thinner than Prisma's, and drizzle-kit push against production can drop columns without much ceremony. Migration tooling has churned across versions.
- Wiring: npm i drizzle-orm && npm i -D drizzle-kit
- Full dossier: /api/public/tools/drizzle-orm

## PocketBase (pocketbase)
- URL: https://pocketbase.io
- Category: Databases & backend
- Cost: free — Free and MIT-licensed. You pay only for a host — roughly $4-6/mo on Hetzner, Fly.io or a small VPS.
- What it is: One executable containing an embedded SQLite database, REST API, realtime subscriptions, email and OAuth2 authentication, file storage and an admin dashboard. Extensible through Go or JavaScript hooks. Still pre-1.0 at the v0.39 series, but widely run in production on a single small server.
- Why builders pick it: Zero cloud bill, zero vendor account, and the entire backend is one file you can copy onto a $5 VPS. Ideal when you want the code and the data to be genuinely yours with no pausing rules.
- Trap: Single node only — no horizontal scaling and no managed backups, so you own uptime, patching and disk. Pre-1.0 means occasional breaking changes between minor releases.
- Wiring: Download the binary, then run ./pocketbase serve
- Full dossier: /api/public/tools/pocketbase

## Quick read

- Free with no card: Drizzle ORM, PocketBase.

## Rules
1. Prefer the free tier when no budget was stated, and say what the ceiling is.
2. Read the full dossier before integrating.
3. Fetch /api/public/models before writing any AI model ID.

Agents can fetch the same thing: GET /api/public/compare?slugs=firebase,drizzle-orm,pocketbase