Fuego vs Firefoo: A Comparison of Firestore Management Tools

Bulk operations / background tasks ¹

Firefoo supports several bulk operations, and long transfers keep running in the background:

• Transferring data between projects or to the emulator, with custom target paths (Transfer Data…)
• Duplicating collections
• Renaming collections
• Renaming documents
• Deleting documents (multi-select bulk delete)
• Renaming or deleting a field in all documents, from the table header (docs)
• Adding a field with a constant value to a collection, a query or selected documents (1.5.5)
• Running JavaScript scripts with the Firebase Admin SDK

Fuego’s bulk operations include:

• Renaming collections
• Renaming documents
• Deleting documents (by query or manual selection)
• Adding attributes to collections
• Deleting attributes from documents
• Renaming attributes
• Copying or moving documents between collections and projects, based on either queries or manual selection
• Copying or moving documents between databases
• Converting attribute values across documents
• Setting attribute values using various transformation functions
• Performing arithmetic operations on numeric attributes (increment, decrement, set min/max)
• Computing values with custom JavaScript scripts in update, import and export jobs

Pipeline queries ²

Firestore’s Enterprise edition introduces Pipeline operations, a stage-based query interface that replaces the single query object with a chain of transformations. It removes the hard limits of classic queries: indexes become optional, and server-side expressions and functions become possible.

From version 2.0 Fuego provides a visual pipeline builder for Enterprise databases, with support for the full set of stages:

• Input stages — collection, collectionGroup, subcollection, documents, database
• Filtering and shaping — where, select, addFields, removeFields, replaceWith, let
• Aggregation and grouping — aggregate, distinct
• Ordering and paging — sort, limit, offset, sample
• Arrays, vectors, and search — unnest, findNearest, search
• Combining and writing — union, delete

Conditions are built with the extended pipeline operator set (like, regex_match, regex_contains, string_contains, ends_with, is_type, is_absent, is_error, and more), can be combined with AND/OR/NOR/XOR groups, and can chain server-side transforms such as to_lower, trim, length, or vector_length before the comparison. Firefoo’s last release (1.5.11, January 2023) predates Firestore Pipeline operations, which entered Preview in January 2026.

Index management / Index Advisor ³

Firefoo leaves index management to the Firebase Console. Fuego manages indexes directly:

• View, filter (by collection or field), create, edit, and delete composite indexes
• Manage vector indexes and single-field index exemptions
• Index management for Firestore Enterprise edition databases
• Compare and synchronize indexes across projects, databases, and environments (dev, staging, production)
• Automatic detection of missing indexes with creation suggestions

Version 2.0 adds the Index Advisor, which works in two modes:

• Analyze a query — submit a classic or pipeline query and the advisor resolves its target collection, loads only that collection’s composite indexes and automatic-index settings, and reports what is missing. Suggestions are labelled Create, Delete, Observation, or Exemption, and graded Safe, Tradeoff, or Info, so you know when a recommendation is a genuine requirement and when it is a trade-off between index count and scan cost.
• Optimize existing indexes — scan every composite index in the database to find exact duplicates and structural overlaps (prefix overlaps, equality permutations, indexes replaceable by index merging).

Both modes run either on deterministic Firestore rules or through an AI provider of your choice. In query mode you can also verify the result against the live database with Firestore Query Explain, which confirms, replaces, or removes the advice. Recommended indexes can be created — and exact duplicates deleted — without leaving the dialog.

Split view vs multi-window ⁴

Comparing two collections side by side is an area where Firefoo has had the edge: its split view divides a single window into panels. Fuego takes the opposite route and, from version 2.0, supports native multi-window: any resource can be opened in a separate OS window from the context menu, with state kept in sync across windows. A project can also be opened in a new window by middle-clicking its name, or with CMD/CTRL+click.

The two approaches are not equivalent, and which one you prefer is largely a matter of taste. Split view keeps everything inside one window and is quicker to arrange; separate windows can be spread across multiple monitors, arranged by the operating system (for example with Stage Manager on macOS), and each keeps its own independent navigation. Fuego does not currently offer a split view inside a single window.