Realtime Database

A desktop GUI for the Firebase Realtime Database

Browse, query and edit the Realtime Database of your Firebase projects in the same window as Firestore, Authentication and Storage. Fuego reads with the credentials you gave the project, and as little as it can: Firebase bills every byte the database sends.

Browse

Every database, a page of keys at a time

Browsing works on every plan; an emulator project needs a paid plan (Individual, Team or the Lifetime Deal), even to browse. Every tab shows what it downloaded, because Firebase bills these downloads.

Four views, many tabs

Open a database as a Tree, a Panel of side-by-side columns, a Table or Raw JSON. Open more tabs on other places in your data or on other databases.

Keys first

Fuego lists a node's children one page of keys at a time, without their values, unless the whole node fits in one page and weighs 1 MB or less. Raw JSON loads a node Fuego has not read yet only when you click Load the JSON, after saying how much it may download.

Count and search keys

Count a node's children by reading their keys only, up to 1,000,000 keys, and find children by how their key starts. Global search finds database names and keys. Values are never searched: that would download them.

Table view

One column per key of the children (the first 50 Fuego finds). A click on a header sorts the rows already loaded, with no new request; Sum and Average use the loaded rows too.

Queries

Queries with Order by, Equal to and Show the first work on every plan, with the key search and paging. A paid plan adds Start at, Start after, End at, End before and the last children.

Compare, decode, anonymize

Compare two nodes side by side, even from two databases. Decode a push ID to see when it was created. Anonymize values masks the values of a tab while its keys stay readable.

Live

Live updates, and what they download

With a paid plan, Live keeps the views you have open up to date: each change in the database appears as it happens, with no reload. On the Free plan, a view is read once.

How Live runs

  • On by default, with a Live button in each tab to turn it off or back on
  • Follows only the tab on screen; the others start again when you show them
  • Pauses the views of a hidden window after about a minute
  • Stops after 15 minutes without activity; one click starts it again
  • Reconnects by itself after a lost connection and after your computer wakes up
  • When it stops, the tab keeps its values and gives the time they date from

What it downloads

  • What Live downloads counts toward your Firebase bill
  • A view is downloaded once when Live starts, then each change as it happens
  • A view that starts again, after a pause, a stop or a reconnection, is downloaded again
  • Each tab shows what it downloaded, such as “1.2 MB read in this tab”: an estimate, since Firebase also bills protocol overhead
  • Live follows a node under 1 MB, or a list with a limit
  • At most 5 live views per database and 10 in all, across every window

Edit

Edit safely

Changing data needs a paid plan. Fuego writes with the project's credentials, as Admin, unless the tab reads as a user.

Review before you save

A save in the details panel shows what you opened next to what will be saved, and lists what it deletes. Nothing is sent until you confirm, and what you do not change stays exactly as the database holds it: a number keeps its digits.

Conflicts

When someone changed the node while you edited it, Fuego writes nothing and shows the database's version next to yours. Reapply my changes applies your changes to the latest version, for you to check and save again. A save made field by field is the exception: there the last write wins.

Table cells

Edit text, numbers and true/false values right in the table. When the value changed since you opened it, choose Replace with mine or Use the server value.

Read-only in Fuego

Keep a path or a whole database read-only in Fuego, on every plan. Fuego then refuses every change there: in the explorer, in jobs, from the command line and from the AI assistant. Other apps and the Firebase console can still write there.

Large deletes

A delete of the root, of 1,000 children or more, or of 10 nodes or more asks you to type a word first. A delete too large for one request runs in the background in small steps, so the database keeps answering your app.

The write size limit

Database settings… shows the size limit of one write, the largest write the database accepts. A change is sent once: when the connection drops after it was sent, Fuego says it may have gone through and asks you to reload the node.

Rules

Security rules, and reading as a user

Security rules

Checking and applying a change needs a paid plan.

  • View and copy the rules, on every plan
  • Check gives each problem's line, column and message
  • Apply… first shows the rules in the database next to yours
  • When the rules changed in the database meanwhile, Fuego applies nothing and shows both changes before you choose
  • History keeps the rules you applied from Fuego and the rules each apply replaced: the 50 newest versions of each database, and always the first rules Fuego replaced there; with a paid plan, Restore into the editor brings one back
  • On an emulator, Show coverage marks the rules the emulator evaluated
  • When a query needs an index, Add the index… opens the rules with the index in place

Read as a user

See what your rules let a user, or a visitor who is not signed in, read. Reading as a user works on every plan; jobs, workspaces and dashboard widgets always run as Admin.

  • Read as a signed-in user of your app, with the token claims you choose, or as a visitor who is not signed in
  • Pick a user from Firebase Authentication to fill in the claims of a real sign-in, or type any uid
  • Each tab has its own identity: two tabs on the same node can read as two different people
  • Views, the key search, filters, queries and Count children all go through your rules
  • With a paid plan, changes from that tab are sent as that identity, and your rules decide
  • Compare what Admin and a user read at the same node, side by side

Jobs

Export, import and bulk jobs

Exporting works on every plan; an export of a query with a range or the last children needs a paid plan. Import, copy, move, rename, delete and update jobs need a paid plan too, and always run as Admin.

Export

Export a node, selected children, the children of a query or a whole database to JSON, JSON Lines, CSV or YAML. Anonymize the data masks the values before they are written to the file. A large node is read in parts, so its export is not a point-in-time copy.

Import

Import JSON or JSON Lines exports from Fuego, the Firebase console or the Firebase command line. Fuego reads the file on your computer first and shows its children, size and levels before anything is written.

Copy, move and rename

Within a database, into another database of the project, another saved project or an emulator. Run as a job, a copy or a move goes child by child: it is not atomic, and for a move a change made at the source meanwhile can be lost.

Delete and update children

Delete a huge node, many rows or the children of a query in small steps. Update children changes every child the same way: set a value, delete or rename a member, write the server time or add to a number.

Follow and continue

A job's card shows the children read, written and deleted, the errors, and the bytes downloaded and uploaded, and lets you pause it. A job that failed, was stopped or was cut off when Fuego closed can continue from its card where it stopped, when its progress was saved: the changes already confirmed are not made again.

Scripts

An export, an import and an update of children can run your own JavaScript on each child, with the editor, the test and the script library of custom scripts.

Database triggers

Every job that writes (import, copy, move, rename, delete, update) offers this switch: Ask Firebase not to run database triggers (Cloud Functions) for these writes, with this hint: “Firebase accepts this request; whether the triggers stay silent has not been confirmed yet.”

Workspaces

Workspaces, dashboards and links

Workspaces

Save the open tabs of a database, each with its node, view, query and search, and open them again in one click. A workspace changes only when you save it.

Dashboard widgets

Show Realtime Database data next to Firestore data with node (a value or a list), aggregation, chart and top list widgets. They refresh from every 30 seconds to every 15 minutes, only while the dashboard is shown, and their settings say how much each refresh downloads.

Files and links

Share a workspace, a query or a dashboard as a .fuego file: it holds databases, paths and queries, never the data. A Fuego link opens a node from a ticket, a chat or a terminal.

Settings sync

With a paid plan, settings sync carries workspaces, saved queries, JSON schemas, read-only paths, database names and the rules history to your other computers (never those of an emulator project).

Automation

Also in the command line and the AI tools

Command line

fuego rtdb reads and changes Realtime Database nodes from a terminal. See Command line.

AI assistant

The assistant reads the Realtime Database and, when you let it write, changes nodes there. See AI Assistant.

MCP server

Your own AI tool reaches the Realtime Database through Fuego's MCP server. See MCP server.

Plans

Free and paid plans

The Realtime Database is in every plan. The Free plan reads, queries and exports; a paid plan adds the changes, Live and the rest.

Free plan

  • Browse every database: Tree, Panel, Table and Raw JSON, keys a page at a time, the key search
  • Simple queries: Order by, Equal to, Show the first
  • Count children, aggregations, and global search of database names and keys
  • Export a node or a whole database
  • View and copy the security rules
  • Read as a user, or as a visitor who is not signed in, for reads
  • Workspaces, saved queries, JSON schemas, Generate code…
  • One project
  • Live: a view is read once, and a dashboard widget refreshes on its interval, every minute by default

Paging through the children stays free: only a range, or a limit to the last children, that you set yourself needs a paid plan.

Individual, Team and the Lifetime Deal

  • Everything in the Free plan
  • Advanced queries: Start at, Start after, End at, End before and a Last limit, in a query or an export
  • Live updates in open views, and on the node widget of a dashboard
  • Edit, add and delete nodes; import; delete, copy, move, rename and update jobs
  • Read as a user for changes too
  • Check and Apply… the security rules
  • Create database…, except with a team sublicense
  • Emulator projects
  • Any number of projects

With a team sublicense, the team can turn the Realtime Database off for you or limit it to chosen databases. Compare the plans.

FAQ

Frequently asked questions

Is the Realtime Database on the Free plan?

Yes. The Realtime Database is in every Fuego plan. On the Free plan you browse, query and export the databases of one project, view and copy their security rules and read as a user. Individual, Team and the Lifetime Deal add changes, import and bulk jobs, Live updates, advanced queries, rules checks and applies, emulator projects and any number of projects.

Does Live cost money?

Live needs a paid plan: Individual, Team or the Lifetime Deal. On the Free plan a view is read once. What Live downloads counts toward your Firebase bill: a view is downloaded once when Live starts, then each change as it happens, and again after a pause, a stop or a reconnection. Each tab shows an estimate of what it downloaded, and you can turn Live off in any tab.

Can I use the Realtime Database emulator?

Yes, with Individual, Team or the Lifetime Deal: emulator projects need a paid plan. Fuego finds the Realtime Database emulator of a running Emulator Suite with the other emulators, including a suite that runs only the Database emulator, and lists the databases it holds.

Does Fuego change my database rules file?

On a paid plan, Apply… changes the rules the database holds, after a review that shows the rules in the database next to yours. The review reminds you that a deploy from a project folder (firebase deploy) overwrites these rules with the rules file of that folder. On an emulator project, Fuego applies the rules to the running emulator only: the rules file of your project folder (database.rules.json) is not changed.

Which Google Cloud role do I need?

The account behind the project's credentials needs a Google Cloud role that lets it read the database, and change it for edits, every job but an export, and rules checks and applies. When Fuego knows that a missing role is why Google refused a request, it opens the IAM permissions required dialog: the role to grant, the account to grant it to, the steps in the Google Cloud console and a ready gcloud command. For the Realtime Database it adds: “The roles shown come from Google's documentation and are not yet confirmed for the Realtime Database.” A refusal by your database's security rules is a different answer, and no role changes it.

Get started

The Realtime Database, next to Firestore

Download Fuego and browse, query and edit your Realtime Database in the same window as Firestore, Authentication and Storage.