The gap
If you only need to open one document and tweak a field, the Firebase console is enough.
The pain starts when the job looks like this:
- build a query with more than a couple of filters
- run it again tomorrow and remember what you ran
- keep Auth users and Cloud Storage next to the documents instead of bouncing across product pages
- work across more than one named database without losing your place
That is daily Firestore work. The console was not built as a desktop client for that loop.
What AppoBase is
AppoBase is a local Firestore GUI for macOS and Windows. It sits on your machine. Billing and project admin stay in Google’s console. The daily path for Database, Auth, and Storage moves into one multi-tab window.
Spelling on the product: AppoBase.
Beat 1 — Problem to product
Common console friction, from the product’s own problem list:
- limited querying, no JavaScript mode
- no query history with replay and execution logs
- awkward collection/document navigation
- Database, Auth, and Storage split across pages
- no native visual edit for GeoPoints / DocumentReferences
- export without solid background progress
- basic JSON viewer
- no real multi-tab / named-database workspace
AppoBase’s answer is not another web admin.” It is a desktop client aimed at those gaps: query builder (filters or JS), history with logs and replay, tree navigation with tabs, Auth and Storage in the same window, GeoPoint/DocumentReference editing, import/export with progress, a stronger JSON viewer, multi-tab and multi-database with isolated state.
Beat 2 — Feature that matters: query builder + history
The surface most people feel first is the query builder.
- visual Where filters, optional Order By / Limit
- JavaScript mode with Monaco when filters are not enough
- run the query, then keep history with execution logs and one-click replay
That is the difference between “I think I ran this yesterday” and “replay this collection’s last good query.”
Beat 3 — Vs the Firebase console (honest frame)
| Need | Firebase console | AppoBase |
|---|---|---|
| Query + JS | limited / no JS | filters + Monaco JS |
| Replayable history + logs | no saved history | history, replay, logs |
| Firestore + Auth + Storage | split across product pages | all three in one window |
| Document views | document panel | Tree, Table, List, JSON |
| Named databases | switcher | isolated tab per database |
| Storage browsing | separate Storage flow | Folder / Tree / Grid / Table |
Other desktop GUIs exist (Firefoo, Firelize, etc.). AppoBase’s public comparison table is the source for feature claims; do not invent competitor gaps beyond what appobase.com lists. FireCMS is a CMS framework, not the same product class as a local desktop GUI.
Pricing (truth only)
- Free to start
-
Pro
$6.49/ month - 3-day trial
- Refund window: 14 days from first payment (site
/refund)
Download: appobase.com
Who this is for
Teams that already live in Firestore and feel the console tax on query, history, Auth, and Storage in one day. Not a replacement for Google Cloud billing or IAM. Not a “build your own admin panel” kit.
Top comments (2)
Curious how others handle this today: when you need yesterday’s Firestore filter set again, do you rebuild it, keep a notes doc, or screenshot Slack? We’re betting history + replay is the missing piece for daily work, not another admin theme.
Quick scope note so nobody expects the wrong thing: AppoBase is a local desktop client for Database / Auth / Storage day-to-day. Billing and IAM stay in Google’s console. If your pain is “I keep retyping the same query,” that’s the job.