Realtime Database
Since v2.3.0Realtime Database
Fuego opens the Realtime Database of your Firebase projects next to Firestore, Authentication and Storage. On the Free plan you browse it as a tree, a panel, a table or raw JSON, query it without code and export it. Individual, Team and the Lifetime Deal add editing, Live updates, rules checks, import and bulk jobs.
What it is
Fuego opens the Firebase Realtime Database of your projects in the same window as Firestore, Authentication and Storage. Open a project, choose Realtime Database in its sidebar, and pick one of the project’s databases: its data opens in a tab, as a Tree, a Panel, a Table or Raw JSON. Open more tabs for other locations, and save the tabs of a database as a workspace. Each database keeps its own tabs: the page shows the tabs of the database you are on, and the ones you left open on another database are there when you go back to it.
Fuego reads with the credentials you gave the project (Adding a Firebase project). With Individual, Team or the Lifetime Deal, it also works with the Realtime Database emulator of an Emulator Suite.
In this section
- Browse, Live and Queries: the four views, Live updates and download costs, key search, queries and saved queries.
- Edit data: change, add and delete nodes, handle conflicts, and keep paths or databases read-only in Fuego.
- Security rules and Read as a user: read, edit, check and apply the rules with their history, and see what your rules let a user or an unauthenticated visitor read and change.
- Export, import and bulk jobs: export and import files, and delete, copy, move, rename or update many children in the background.
- Workspaces, dashboards, files and sync:
save tabs as workspaces, add Realtime Database widgets to a dashboard, share
.fuegofiles and sync your settings.
Databases
The Realtime Database entry of a project’s sidebar opens the project’s Realtime Database page. Fuego asks Firebase which databases the project has, with the project’s own credentials, and adds the ones you added by hand. On an emulator project, it lists the databases the emulator holds.
- Open database, at the top of the page, opens the database picker. The database you pick opens in a new tab.
- All databases…, at the bottom of the picker, shows the page’s home (the page title leads there too). At the top is the tab you used last: its database, its node as levels you can click, and Continue (or Enter), next to your other open tabs and your Realtime Database bookmarks. Before you open any database, it shows the default database with Open.
- Under it, Databases has one card per database: its badges, where it is hosted and how many tabs are open on it. A click opens the database, a middle click opens it in a new tab.
- Workspaces has one card per saved workspace, with the nodes its tabs open. A click opens the workspace, a middle click adds its tabs to the open ones; its ⋯ menu does both, stars it and opens Manage workspaces….
- The top of the sidebar’s Realtime Database section names the database of the tab you are in, with its location under it, and opens the database menu.
Fuego caches the list it got from Firebase for 10 minutes; Reload the list asks Firebase again. A project with no Realtime Database offers Create database…, Add by URL… and Open the Firebase console (on an emulator project, Add by URL…).
The database picker
Each row shows the database’s name, the name you gave it in Fuego if any, its location (or its address) and its badges:
| Badge | What it means |
|---|---|
| Default | The default database of the project. |
| Added by hand | Added to this project in Fuego by its URL, on this computer or on another one that syncs the project. On an emulator, added by its name. |
| Suggested | On an emulator project: the project’s default database, which the emulator does not hold yet. Opening it creates it. |
| Emulator | A database of the emulator suite. |
| Unverified | Fuego could not confirm that this database belongs to this project: see Unverified databases. |
| Moved | This database answered from another address, which Fuego now uses. |
| Disabled | This database is disabled in the Firebase console. |
With more than five databases, a filter box at the top searches their names, locations and Fuego labels. Each row has a ⋮ button (Database actions) and a right-click menu; a database added by hand also has a trash button (Remove from Fuego), which removes it from Fuego’s list without deleting the database or its data.
Add a database by its URL
To add a database your account cannot list:
- Choose Add by URL….
- In Database URL, paste the URL shown on the Realtime Database page of
the Firebase console, such as
https://my-project-default-rtdb.firebaseio.com, orhttps://<name>.<region>.firebasedatabase.appfor a database in another location. - Click Add.
Fuego reads the database once, then asks Firebase whether it belongs to this project:
- If it lives at another address, click Use this address.
- If it belongs to another Firebase project, Fuego refuses it: add it to its own project instead.
- When Firebase does not say which databases the project has (for example because your account cannot list them), Fuego adds the database marked Unverified.
Open a database from its URL
Paste a database URL into the command palette: its bottom row offers Open the database URL, followed by the URL. A URL with a path opens that node.
- When a saved project has that database, it opens there.
- When no saved project knows it, Fuego asks which project it belongs to, adds the database to that project and opens it (emulator projects are not offered).
The Open link from clipboard command of the palette does the same with a
database URL you copied, and a link to a Realtime Database location in the
Firebase console opens at that node. Fuego drops the part of the URL after ?,
so a secret copied with it (?auth=…) is never shown or sent.
The database menu
Right-click a database, or click its ⋮ button (Database actions), in the picker, on a card of All databases… or at the top of the sidebar’s Realtime Database section:
- Open opens the database’s main tab at its root; Open in a new tab opens it in another tab.
- Copy link copies a Fuego link to
the database’s root. Copy REST URL copies the address of its root for
the Realtime Database REST API, ending in
.json(on an emulator, followed by?ns=and the database’s name). - Workspaces lists, saves, manages and imports the workspaces of this database: see Workspaces, dashboards, files and sync.
- Security rules… opens the rules of the database: see Security rules and Read as a user.
- Database settings… shows its settings: see Database settings.
- Generate code… writes code that reads the database: see Browse, Live and Queries.
- Export database… exports the whole database (every plan), and Copy database to… copies it into another database (paid plans): see Export, import and bulk jobs.
- Rename…, Hide (or Show), Move up and Move down arrange Fuego’s lists: see Names, order and hidden databases.
- Remove from Fuego, for a database you added by hand.
On a Suggested database, which the emulator does not hold yet, Security rules…, Database settings…, Export database… and Copy database to… are disabled until you open the database once to create it.
Names, order and hidden databases
These change only Fuego’s lists, never the database:
- Rename… sets a Name shown in Fuego (up to 80 characters) shown beside the database’s own name. Every confirmation still shows the real database name.
- Hide moves a database under Show hidden in the picker (and Hidden on All databases…); Show brings it back.
- Move up and Move down change a database’s place in the lists (show a hidden database first).
With settings sync, these names, the order and the hidden databases follow you to your other computers (an emulator project’s stay on this computer).
Database settings
Database settings… reads and shows the database’s Name, URL, Location, Type (default or additional) and State (active or disabled), plus two Firebase settings (change them with the Firebase CLI or in the Firebase console):
- Size limit of one write (Tiny, Small, Medium, Large by default, or Unlimited): the largest write the database accepts.
- Strict trigger validation: when on, Firebase refuses a write whose event would be too large for the database triggers of Cloud Functions.
On an emulator project, the dialog shows only the Name and the URL. To keep Fuego from changing a database, use Whole database read-only in Fuego: see Edit data.
Create a database
Create database… is at the bottom of the picker, on the page of all databases, and on the page of a project that has no Realtime Database yet. It needs a paid plan (and is not available on emulator projects, read-only projects or team sublicenses).
The dialog asks for a Database name (lowercase letters, digits and hyphens, up to 63 characters) and a Location:
- Database names are unique across all of Firebase and can never be reused, even after a database is deleted.
- The Firebase project must be on the Blaze billing plan, and only the Firebase console can disable or delete a database.
- Check asks Firebase whether the name is free without creating it, and offers Free names: when the name is taken.
- Create confirms once more, then creates the database and opens it. If the network answer gets lost, Fuego will not create that name in that location again until you Reload the list of databases.
Unverified databases
The Unverified badge marks a database Fuego could not confirm as the project’s because Firebase did not list the project’s databases.
- A database you added by hand on this computer stays writable.
- A database added by its URL on another computer reaches this one through settings sync as Unverified. Until Fuego confirms on this computer that it belongs to the project, you can read and export it, but changes, jobs that write to it, and rules checks or applies are refused with Not confirmed for this project. To make it writable here, add it again with Add by URL… and its address, or wait until your account can list the project’s databases.
- When Firebase answers that such a database belongs to another project, Fuego leaves it out of the list.
Emulators
Emulator projects need a paid plan. Fuego finds the Realtime Database emulator of a running Emulator Suite with the others, including a suite that runs only the Database emulator, and lists the databases the emulator holds, each marked Emulator.
- To connect a suite by hand, enter its address in the emulator step of the
add-project dialog (default
localhost:9000for a standalone Database emulator). - The project’s default database shows as Suggested until the emulator holds it: Fuego never reads it on its own, since a read creates it.
- Add by URL… accepts a namespace name (such as
my-app) or an emulator URL (http://127.0.0.1:9000/?ns=my-app) without reading it on add.
Plans
The Realtime Database is in every plan. The Free plan reads, queries and exports; Individual, Team and the Lifetime Deal add the changes, Live and the rest:
| What you can do | Free | Paid plans |
|---|---|---|
| Browse every database: Tree, Panel, Table and Raw JSON, keys a page at a time, the key search | Yes | Yes |
| Simple queries: Order by, Equal to, Show the first | Yes | Yes |
| Count children, aggregations, and global search of database names and keys | Yes | Yes |
| Export a node or a whole database | Yes | Yes |
| View and copy the security rules | Yes | Yes |
| Read as a user, or as a visitor who is not signed in | Reads | Reads and changes |
| Workspaces, saved queries, JSON schemas, Generate code… | Yes | Yes |
| Advanced queries: Start at, Start after, End at, End before and a Last limit, in a query or an export | No | Yes |
| Live updates in open views | No: a view is read once | Yes |
| Live on the node widget of a dashboard | No: a widget refreshes on its interval, every minute by default | Yes |
| Edit, add and delete nodes; import; delete, copy, move, rename and update jobs | No | Yes |
| Check and Apply… the security rules | No | Yes |
| Create database… | No | Yes, except with a team sublicense |
| Emulator projects | No | Yes |
| Projects | One | Any number |
Paging through the children stays free: only a range, or a limit to the last children, that you set yourself needs a paid plan. On every plan, a project set to read-only in Fuego (Adding a Firebase project) refuses every change, and so does a path or a database kept Read-only in Fuego (Edit data). See pricing for the plans.
Team sublicenses
A team sublicense is a license your team gives you. In the sublicense settings:
- Realtime Database enabled, turned off, removes the Realtime Database from the sidebar and refuses every request.
- Under Allowed resources, a Realtime Database entry names a project and limits its Realtime Database to the databases chosen under Limit instances (or All instances when none are chosen). Once the sublicense has one such resource, the Realtime Database of any project it does not name is refused.
- Read only refuses every change.
With any team sublicense:
- Fuego never creates a database.
- A database Fuego cannot confirm as the project’s is left out of the list, refused for reads and changes alike, and cannot be added by its URL.
Access and troubleshooting
Access to Google Cloud
Fuego reads and changes the Realtime Database with the credentials you gave the project (Adding a Firebase project): a Google sign-in, a service account key or the gcloud application default credentials. The account 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 Google refuses a request because the account lacks a role, Fuego 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 notes: “The roles shown come from
Google’s documentation and are not yet confirmed for the Realtime Database.”
Refused by the database rules is a different answer: the database’s security rules refused the identity the tab reads as, and no IAM role changes that (Security rules and Read as a user).
Messages and what to do
- Sign in again for the Realtime Database: a project added with a Google
sign-in in a Fuego older than 2.3.0 asks once for one more sign-in so Google
can grant access to the Realtime Database. Click Continue with Google and
use the project’s Google account. With gcloud application default
credentials, run
gcloud auth application-default loginin a terminal, then Retry. With a service account key, use Edit project access and give the key again. - Credentials not accepted / No access to this database: check the credentials or the account’s roles in the Google Cloud console (Edit project access), then Retry.
- Refused by the database rules: while the tab reads as a user, choose Read as Admin or Change identity; for a change made as a user, Save as Admin… saves it with the project’s credentials.
- This query needs an index: the message names the
.indexOnrule to add. Add the index… opens the security rules with the index in place; check and apply them (or copy the rule on the Free plan). See When a query needs an index. - This value is too large: Load anyway reads it, Show keys only lists its children’s keys, or Export this node… writes it to a file.
- This change is too large: the data is larger than the Realtime Database accepts in one request; write it in smaller parts.
- This database lives at another address: click Add with this address to add it with the address Firebase reported.
- This database is disabled: re-enable it in the Firebase console (Open in the Firebase console), then Retry.
- The emulator stopped serving this database / The emulator cannot open this database: start or restart the Realtime Database emulator, then Retry.
- The Realtime Database API is turned off: Open the API page, turn it on, then Retry.
- Database not found: the database may have been deleted or moved; Show the databases to pick another one.
- Not confirmed for this project: a database added on another computer that Fuego has not confirmed here (Unverified databases).
On the command line
fuego rtdb (Command line) follows
the same plans and limits as the app:
- A refusal by your plan, your license, or a project/path/database kept
read-only in Fuego ends with exit code
5. - A change to an unconfirmed database added on another computer ends with exit
code
1(rtdb_database_unverifiedwith--json). - A change that removes the whole database, 1,000 children or more, 10 nodes
or more, or more than Fuego can count asks you to type its key (
-yor--confirm <key>answers it; for the AI assistant,fuego ai --approve-toolsor the app’s Approve all code).
Where else the Realtime Database appears
- Command line:
fuego rtdb. - AI assistant: large Realtime Database changes.
- MCP server: which Realtime Databases an AI tool can reach, and its tools.
- Shortcuts.
- Global search.
- Dashboards: Realtime Database widgets.
- Settings sync: your Realtime Database settings on your other computers.
- Windows and links:
fuego://rtdb/…links and.fuegofiles. - Command palette: open a database from its URL.
- Custom scripts: scripts in export, import and update jobs.
- Bookmarks: bookmark a node or open it in quick view.
- Customize: the Live on by default switch.
- Fuego DevTools: open a Realtime Database location in Fuego from your browser.
