Firenook: A faster drop-in for the Firebase emulators
Firenook runs the Firebase emulators with your firebase.json, SDKs and ports: 40× faster writes, 10× less memory, no Java, and data that survives restarts.
Firenook runs the Firebase emulators with your firebase.json, SDKs and ports: 40× faster writes, 10× less memory, no Java, and data that survives restarts.

Keep your firebase.json, SDKs and ports, and change one word in your script. No Java to install, and your data survives restarts.
40×faster writes5.1 ms against 208.2 ms, median
10×less memory2.11 GiB against 22.57 GiB at peak
0.59 sto restart with your dataagainst 30.8 s
Same flags, same ports, same export format. Your project stays as it is, and firebase-tools stays for deploying.
- "emulators": "firebase emulators:start --import ./data"+ "emulators": "firenook emulators:start --import ./data"
Read the way the Firebase CLI reads them.
Your code and config stay as they are.
connectFirestoreEmulator, FIRESTORE_EMULATOR_HOST and the rest connect unchanged.
Imports and exports the official format, both ways.
Your SDKs connect to them as they connect to Google’s: the same hosts, the same ports, the same environment variables.
Native and web SDKs, realtime listeners, Security Rules, named databases, and the official import and export.
orders12 documents
createdAt2026-10-23 13:06:17.872 UTC
items[{ price: 54, qty: 1, sku: "hoodie" }, { price: 28, qty: 1, sku: "tee" }]
total82
Every operation of the official Auth emulator: password, email link, phone, MFA, passkeys, tenants and blocking functions.
Users12
The Firebase and Cloud Storage APIs, with Security Rules evaluated natively, firestore.get() included.
demo-shop.appspot.com / products8 files
HTTP, callable and streaming functions, and every trigger: Firestore, Storage, Auth, Pub/Sub, Eventarc, schedules and task queues. Code reloads on save.
Function calls25
| Time | Function | Trigger | Summary | Status | Duration |
|---|---|---|---|---|---|
| 13:06:19 | stripeWebhook | http | POST / | 500 | 1.1 ms |
| 13:06:18 | sendReceipt | firestore | orders/mzbnHY1n79leG5ioi2nD created | 200 | 1.8 ms |
| 13:06:18 | checkout | http | POST / | 201 | 6.3 ms |
| 13:06:18 | sendReceipt | firestore | orders/c0yT9Jkt9NGpiX7HMV9r created | 200 | 1.7 ms |
| 13:06:18 | checkout | http | POST / | 201 | 5.0 ms |
Every RPC over gRPC and HTTP/JSON: push, ordering, filters, dead-letter topics, seek, snapshots and schemas.
nightlyReport, every day 02:00: next run 2026-10-24 02:00 UTCQueues for onTaskDispatched, with the official retry and rate-limit behaviour.
Custom events delivered to onCustomEventPublished, and the Firebase services’ own.
Extensions from local, vendored or registry sources, offline once vendored.
The orders, users, files and calls above are from a run of the demo project, as Firenook returned them. Realtime Database, Hosting, App Hosting and Data Connect are not emulated; a firebase.json that configures them still starts, with a warning. What each service covers.
Two hours of a production app’s traffic against each emulator in turn, every operation timed by the client.
10× less
Official22.6 GiB
Firenook2.11 GiB
40× faster
Official208 ms
Firenook5.1 ms
19× faster
Official209 ms
Firenook11 ms
52× sooner
Official30.8 s
Firenook0.59 s
8× faster
Official96.3 ms
Firenook12.0 ms
61% less
Official1,586 s
Firenook616 s
The app holds 211,205 Firestore documents and 6.7 GB in Storage; both emulators ran on one server. Firenook answered 25 of 26 query shapes faster and tied on the last. How it was measured.
Add --keep-data and Firestore, Auth and Storage come back with all your data in about half a second, even with millions of documents. No export at every stop, no import at every start.
A crash loses at most the last second of writes, where the official emulator loses everything since its last export. A stop always closes the data cleanly.
npx firenook emulators:start --keep-data
Official emulator
Stop: export, 50–57 sStart: import, 21.6–23.6 s
Stop, 0.04–0.30 sStart, 0.54–0.57 s
$ npx firenook emulators:exec "node --test checkout.test.mjs" firenook: Starting emulators: auth, functions, firestore, pubsub, storagefirenook functions: Loaded functions definitions from source: checkout, sendReceipt, stripeWebhook, nightlyReport.All emulators ready✔ checkout takes an order (173.227708ms)ℹ pass 1ℹ fail 0firenook suite stopped cleanly
exit 01.39 s from start to stop, the test included
emulators:exec starts the suite, runs your command once everything is ready, with the emulator variables set, then stops and passes on the exit code.
CI gets plain lines, the same ones the official emulator prints, and there is no Java to set up first. Firenook needs only Node 24.
npx firenook emulators:exec "npm test"
Google’s Emulator UI has no page for your Functions, Pub/Sub, Cloud Tasks or Eventarc, only a log. Firenook’s console covers every service it runs, live, on the Emulator UI’s port.
Every call, with what triggered it, its outcome, its duration and its logs.
Light and dark, works offline, sends nothing anywhere. Bookmarks to the official UI’s pages open the matching console page. Every page of the console.
firenook mcp gives a coding agent 55 tools over the running suite. It reads the log and each function call with its error, asks the Security Rules why a request is denied, and works with your data. Nothing leaves your machine.
npx firenook mcp add
Sets it up for Claude Code, Cursor and VS Code in the project’s own files. Other agents run npx firenook mcp. How agents use it.
The Stripe webhook answers 500 on my machine. Why?
functions_list_calls outcome: "failed"
failed500 stripeWebhook http POST /, 1.15 ms at 13:06:19
functions_get_call id: "e72ca3-25"
errorError: No signatures found matching the expected signature for payload
atfunctions/index.js:24:11
headershost, connection, content-type, accept, accept-language, sec-fetch-mode, user-agent, accept-encoding, content-length
body{"type":"checkout.session.completed"}
rules_evaluate service: "storage", method: "create", path: "products/mug.svg"
verdictdeny as unauthenticated
line 9allow read, write: if false;
FirestoreRead, query, count, write and delete documents
AuthenticationManage users, read sign-in codes, mint ID tokens, set claims
StorageList, read, upload, copy, move and delete files
Functions and logsInvoke a function, read each call and the log, replay a call after a fix
Security RulesAsk why a request is denied, test a draft, list denials
Pub/Sub, Tasks, EventarcPublish, peek, run tasks and schedules now, replay events
Do I still need firebase-tools?Yes, for deploying and everything else the Firebase CLI does. Firenook replaces only the emulators: install it next to firebase-tools and run your emulators with it.
Does Firenook need Java?No. Its services are native code in one npm package, with an engine for macOS, Linux and Windows, and nothing else is downloaded at install or start. Node 22, 24 or 26 runs your Functions, as it does in production.
Can I go back to the official emulator?Yes. Firenook imports and exports the official format. While Firenook runs, export with npx firenook emulators:export ./export, then start the official emulator with --import ./export.
Which services does it emulate?Firestore, Authentication, Cloud Storage, Cloud Functions, Extensions, Pub/Sub, Cloud Tasks and Eventarc. Realtime Database, Hosting, App Hosting and Data Connect are not emulated; a firebase.json that configures them still starts, with a warning.
Is it ready for my team?0.2.0 is the first release for public use. Every release passes conformance replays against the official emulator and packed installs on all five platforms, and Firenook passed a two-hour benchmark against the official emulator on a real application. Commit your lockfile and upgrade on purpose.
Is it free?Yes. Firenook is open source under the Apache License 2.0.
Is Firenook made by Google?No. Firenook is an independent open-source project, not affiliated with or endorsed by Google. Firebase is a trademark of Google LLC.
One package, nothing else to install: Node 22, 24 or 26 on macOS, Linux with glibc 2.28 or newer, or Windows x64. Starting a new project instead? npx firenook init sets one up.
Keep firebase-tools for deploying: Firenook has no deploy or login command.
npm install --save-dev firenook
This reads firebase.json the way the Firebase CLI does, and changes nothing.
npx firenook init --adopt --dry-run
Same flags and ports, so your app connects as before and your data imports as it is.
npx firenook emulators:start
Texto de firenook.dev tal como lo publicó, leído de su página y mostrado aquí con el formato de El Autómata. El original, en firenook.dev · Volver a la noticia de El Autómata