# Blog

> Posts from the people building Firenook: how it works, what it measures, and what is coming. Also as an RSS feed.

How Firenook works, what it measures, and what comes next, from the people building it.

[Follow by RSS](https://firenook.dev/blog.xml)

1. [23 October 2026](https://firenook.dev/blog/how-firenook-writes-40x-faster)
   ## [How Firenook writes 40× faster than the Firebase emulator](https://firenook.dev/blog/how-firenook-writes-40x-faster)
   [What a Firestore write costs in Firenook, read from the source: a journal write, a redb commit without a sync, a few index entries and a wake-up.](https://firenook.dev/blog/how-firenook-writes-40x-faster)
2. [23 October 2026](https://firenook.dev/blog/introducing-firenook)
   ## [Introducing Firenook](https://firenook.dev/blog/introducing-firenook)
   [Firenook runs the Firebase emulators from one npm package, with your firebase.json, SDKs and ports, no Java, and data that survives restarts.](https://firenook.dev/blog/introducing-firenook)
3. [21 October 2026](https://firenook.dev/blog/give-your-agent-the-emulator)
   ## [Give your coding agent the emulator, not production](https://firenook.dev/blog/give-your-agent-the-emulator)
   [Firenook's MCP server gives a coding agent 54 tools over the local Firebase emulators: data, users, files, function calls, logs and Security Rules.](https://firenook.dev/blog/give-your-agent-the-emulator)