# Do coding agents recommend Firebase? > Firebase was chosen in 2% of 732 judged databases sessions, ranking fifth. Measured with Claude Code, Codex and Cursor. Source: https://armature.tech/library/do-coding-agents-recommend-firebase Published: 2026-10-14 Publisher: Armature, Inc. (https://armature.tech) --- > Firebase was chosen in 2% of 732 judged databases sessions, ranking fifth. It was also raised as a candidate in 241 further sessions without being chosen. This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in databases inside a realistic codebase. Not what a chat assistant says about Firebase. What an agent actually installed. ## The numbers | | | | --- | --- | | Category | Databases | | Sessions in the category | 732 | | Sessions where Firebase was chosen | 17 | | Install share | 2% | | Rank in category | 5 of 19 | | Codebases it won in | 5 | | Raised as a candidate, not chosen | 241 | | Chosen when considered | 7% | | Site | firebase.google.com | ## By agent With 17 wins spread across 3 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established. | Agent | Sessions | Chose Firebase | Share | | --- | --- | --- | --- | | Claude Code | 380 | 9 | 2% | | Codex | 181 | 3 | 2% | | Cursor | 171 | 5 | 3% | ## By who was asking Firebase performs similarly across the four kinds of buyer, from 0% to 3%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured. | Who is asking | Sessions | Chose Firebase | Share | | --- | --- | --- | --- | | Vibe coder | 417 | 14 | 3% | | Junior developer | 163 | 3 | 2% | | Senior engineer | 113 | 0 | 0% | | Enterprise team | 24 | 0 | 0% | ## What Firebase was up against The full ranking in databases, from the same sessions: | # | Product | Runs won | Share | | --- | --- | --- | --- | | 1 | Neon | 334 | 46% | | 2 | Supabase | 269 | 37% | | 3 | Turso | 48 | 7% | | 4 | Azure Database for PostgreSQL Flexible Server | 21 | 3% | | 5 | Firebase **(this page)** | 17 | 2% | | 6 | Google Sheets | 10 | 1% | | 7 | Netlify Forms | 6 | 1% | | 8 | Formspree | 4 | 1% | ## What this means This is an integration problem, not a presence problem. Agents raised Firebase in 241 sessions and chose it in 17, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name. That is the cheaper of the two problems to have. The reason is written down in each losing transcript. ## Where these numbers come from The 732 sessions in databases are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: [how we measured this](/library/how-we-measured-this). Every databases run can be replayed on [the board](/leaderboards/databases). If you work on Firebase: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts. ## Common questions ### Do coding agents recommend Firebase? Yes. Firebase was chosen in 17 of the 732 judged sessions in databases, a 2% install share, ranking fifth in its category. ### Does Claude Code recommend Firebase? In 9 of the 380 sessions in databases run with Claude Code, which is 2%. ### Do different coding agents treat Firebase differently? Not much. Claude Code, Codex and Cursor chose it at similar rates, between 2% and 3% of their runs. ### How was this measured? Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind. ### How often is Firebase considered but not chosen? It was raised as a candidate in 241 sessions without being chosen, and chosen in 17. That is a 7% conversion from considered to chosen. ## Read next - [How to get picked for databases by coding agents](https://armature.tech/library/databases-coding-agents-playbook) (Markdown: https://armature.tech/library/databases-coding-agents-playbook.md) - [Do coding agents recommend Neon?](https://armature.tech/library/do-coding-agents-recommend-neon) (Markdown: https://armature.tech/library/do-coding-agents-recommend-neon.md) - [Do coding agents recommend Supabase?](https://armature.tech/library/do-coding-agents-recommend-supabase) (Markdown: https://armature.tech/library/do-coding-agents-recommend-supabase.md) - [Do Claude Code, Codex and Cursor pick the same tools?](https://armature.tech/library/do-claude-code-and-codex-agree) (Markdown: https://armature.tech/library/do-claude-code-and-codex-agree.md) --- Armature helps software products get discovered and used by coding agents. Service: https://armature.tech/discoverability · Results: https://armature.tech/leaderboards/sectors · Contact: contact@armature.tech