Supabase released OrioleDB, Multigres, and the Explorer editor within three days, while Firebase made App Check mandatory for its AI Logic features and promoted agent integrations; both companies are courting AI coding tools, and the report offers no evidence yet on which platform is winning.

From the stories

Multigres is now in private alpha: high availability for Supabase Postgres. If your database fails, a standby copy takesSupabase

Supabase vs Firebase: Research comparison

Quick Verdict

Supabase still carries the page title "The Open Source Firebase Alternative" on supabase.io, and on October 21 @Firebase promoted SQL Connect as a way to "generate a secure PostgreSQL schema." The two products now overlap more than their old SQL-versus-NoSQL framing suggests. On scale, supabase/supabase has 114,466 GitHub stars and 1,161 open issues. The auto-generated transcript of Y Combinator's "When Agents Become Your Users" interview (72,866 views) says Supabase "now has 13 million users and it's spinning up over a million databases a week." The gathered evidence has no platform user count for Firebase. Its three SDK repos (iOS 6,979, JS 5,157, Android 2,580 stars) measure client libraries rather than the platform, so the star gap is not a like-for-like comparison. The month's evidence shows both companies courting AI coding agents, with Firebase's own docs now framing AI-assisted setup as a first-class workflow using Antigravity, Claude Code, Codex, and Cursor through agent skills, the Firebase CLI, and an MCP server. It does not include migration data showing which one is winning.

Supabase

Supabase shipped three Postgres launches in three days: OrioleDB in public beta on every plan (October 28), Multigres in private alpha (October 29), and the Explorer query editor (October 30). @supabase described Multigres (149 likes) as "high availability for Supabase Postgres," with automatic standby failover. The official Multigres docs describe it as an "operating system for Postgres" that runs across multiple nodes with automatic failover, free during the Alpha for paid-plan organizations but capped at two projects per org and explicitly not covered by Supabase's uptime SLA. The changelog entry confirms the October 1 private-alpha opening, and Supabase's earlier Multigres v0.1 Alpha blog post traces the project back to a June 4 open-source release built with Vitess creator Sugu Sougoumarane, pitching "Vitess-grade horizontal scaling, high availability, and operational simplicity" for Postgres. Access is limited to paid-plan organizations that request it, so this is not a general release. Explorer (142 likes) adds Notebooks that "your agent" can run. The Supabase Select recap (30,061 views) opens with Supabase having "purchased Turso, the SQLite company," and introduces Supabase Compute, which reached Hacker News as a private alpha with 4 points.

Practitioner sentiment on the database layer is positive. In a r/nextjs thread (17 points, 34 comments), u/TheYawningRapport wrote that "Supabase works pretty well for the database side," and warned that unindexed filters get painful past roughly 50k rows. Dave Ebbelaar's full-stack AI course built on Supabase drew 73,315 views. Product Hunt shows 912 reviews averaging 5.0. A brycent reel (4,234 likes) cites a $10.6B valuation. On pricing, Supabase's own pricing page lists a Free tier (unlimited API requests, 50,000 monthly active users, 500 MB database), Pro at $25/month (100,000 monthly active users), and a Team tier at $599/month aimed at organizations needing advanced collaboration and compliance controls, per No Code MBA's 2026 breakdown and the independent pricing tracker Tierpeek. A third-party calculator from MakerKit estimates a mid-size workload landing around $25 base plus $50 compute for a Medium instance, before storage and egress are added, and notes that Team and Enterprise base fees aren't published. The company is also hiring heavily: 69 roles appear on its Ashby board, including a Software Engineer - AI Tooling Infrastructure, a Product Manager - Administration & Governance, and Database Support Engineer seats across regions. Each listing pitches Database, Auth, Storage, Edge Functions, Realtime, and Vector Search as one integrated platform.

The weaknesses cluster around security mistakes made by AI-assisted builders, plus cost. A r/Supabase audit (12 points, 20 comments) found that 26% of about 5,000 public Bolt + Supabase repos have a table anyone can read. Commenter u/Personal_General_725 challenged how repos were attributed to Bolt. Separately, rekavigwebdesign and rowattest posted RLS leak tutorials, and ctrlztherapy explained that Edge Function secrets stay on the server, so a visible key means it was exposed through a VITE_ or NEXT_PUBLIC_ variable.

On cost, a video-egress thread (31 comments) produced u/WarmDrunkenness5's line that "videos will eat your egress for breakfast." A r/vibecoding "DO NOT USE SUPABASE" post drew 74 comments, but the top reply from u/TheAnswerWithinUs (51 upvotes) mocked the poster instead of agreeing. John Kealy (9,821 views) argues that "every tutorial you've ever watched about Supabase is totally wrong."

Firebase

On November 2, @Firebase made App Check enforcement mandatory for Firebase AI Logic and pushed a plugin into @Antigravity's new Marketplace. The Marketplace post (144 likes) says the plugin offers agent guidance to secure Firestore rules, deploy to App Hosting, and set up AI logic. The App Check post (7,332 views) means generative features need attestation configured to keep running. This lines up with Firebase's official AI-assistance documentation, which now positions Firebase agent skills, the Firebase CLI, and a dedicated Firebase MCP server as the recommended way to wire Antigravity, Claude Code, Codex, or Cursor into a Firebase backend. Firebase's October output leaned heavily toward agents: Agent Skills for Firebase with Antigravity CLI (63 likes), a six-hour iOS app build using Antigravity (50 likes), and Gemini API calls through AI Logic (6,731 views).

Strengths show up in mobile and budget tooling. The September Release Notes (67 likes) lead with Spend Caps in public preview. Phone Number Verification, which offers carrier-level checks instead of SMS OTPs, drew 149 likes. At FlutterCon, Firebase's Arthur Thompson appeared on the Flutter and Firebase channel (9,246 views). Notably, the interviewer raised the perception that developers "outgrow Firebase." mr_mewhy (54 likes) shipped 4 web apps on the free Spark Plan. Developers are also building tools around the platform. The hidane 0.1.0 Java-free Firestore emulator post got 7 points on r/Firebase. Aruma, a self-hosted backend for the official SDKs that pitches a "~$5 VPS," got 3 points on HN.

The weaknesses are reliability and quota surprises:

• Realtime Database incident. The Firebase Status Dashboard logged partial RTDB degradation in us-central1 on October 21. IsDown's AI summary describes intermittent 500 errors lasting over 24 hours.
• Outage count. incidenthub claims 7 outages in 30 days. StatusGator's Firebase Platform page also tracks user-reported issues.
• SDK churn. JS SDK 13.0.0 (October 7) carried a breaking AI Logic change, and 13.1.0 fixed transient Auth 5xx errors.
• Auth quota. A r/Firebase post (3 points, 9 comments) reports a 200/day GetOobCode quota blocking verification emails on Blaze.
• Architecture caution. ayesha.appdev summed it up: "Firebase can speed up development, but it won't fix poor architecture."

Head-to-Head

The Bottom Line

Choose Supabase if your data is relational, you ship web apps on Next.js or Vercel, and you are willing to own your RLS policies instead of trusting AI-generated ones. The r/nextjs consensus is that the Postgres underneath holds up well if you index early. The 26% open-table audit shows the cost of skipping that work. Media-heavy apps should plan to offload files, as u/Ok-Motor-9812 (7 upvotes) did with Cloudflare R2. Budget planning matters too: Supabase's own pricing page and third-party trackers like Tierpeek and MakerKit show costs climbing quickly past the Free tier once compute, storage, and monthly active users scale up, and Supabase's own billing FAQ explains that pricing is organized around organizations containing multiple projects, each billed for its own compute and add-ons.

Choose Firebase if you are building mobile-first apps with Flutter, iOS, Android or React Native and want Gemini wired in through AI Logic and Google's agent plugins. @Firebase is clearly investing in that path, and its AI-assistance docs now formalize that investment with agent skills and an MCP server built for coding agents. Do two things before committing: test Auth email quotas on Blaze, given the GetOobCode thread, and set up App Check before relying on AI features. Demand for the skill is real: CareerHolo's Firebase Jobs page counts 385 openings with a $175k median, though TheJobsMap lists no open roles at Firebase itself as of November 2.

The emerging stack

The gathered evidence does not establish anyone running Supabase and Firebase together. When junky_rd asked whether to "use firebase or supabasss," the choice was framed as either/or. What does repeat is a three-layer pattern of agent, frontend host, and backend, with each platform in the backend slot:

• Supabase variants. bstratgie.web.aca tells Claude Code users to install Supabase and Vercel plugins first. hisyamhamzahhh (64 likes) built on Claude AI Pro + Supabase + Netlify. _nexa_byte lists React Native, Next.js, Vercel and Supabase. draguuu (10 likes) asked whether Vercel + Supabase is a solid foundation to grow on.
• Firebase variants. mr_mewhy runs VS Code, then Firebase, then GitHub, then Netlify. @Firebase's own showcase pairs Firebase with Antigravity, and its AI-assistance docs now explicitly add Codex and Cursor to that pairing.

So the real contest is less Postgres versus Firestore than which backend the coding agent reaches for by default.