Firescope - A Firestore GUI that backs up every write before it runs

by
A desktop Firestore GUI for macOS and Windows. Every write — inline edits, bulk updates, deletes, CSV imports, even the JS console — goes through confirm → backup → execute → audit log. Enforced in Electron's main process, not the UI, so nothing can bypass it. Connections are labelled dev/staging/production; destructive production writes require typing the project ID. Restore is a diff preview and one click; ⌘Z undoes the last write. 14-day full trial. No signup, no card.

Add a comment

Replies

Best
Hunter
📌
Maker here. I built this because of one specific feeling: hovering over the delete button in the Firebase console on a production project. The console is good, but production and test look identical, deletes are final, and nothing is logged. I'd been living with that for years. The design decision I care about most: the safety pipeline lives in the main process. A UI warning is something you learn to click through — a structural guarantee isn't. Whatever the renderer sends, a write that skipped confirm → backup → audit log simply cannot exist. Honest disclosures: - The Windows build is not code-signed yet, so SmartScreen will warn you. Signing is planned. - It's a paid product (14-day trial, no card). Read-only browsing stays free forever. - Anonymous funnel analytics: the site records a visit and a download, the app records that a trial started, and Stripe records a first paid subscription — each against a randomly generated ID, plus UTM tags, platform, app version, and plan name. No name, email, IP, device fingerprint, license key, or any of your Firestore data is ever sent, and the app has an opt-out. Your Firestore data path itself still has no backend. Details: - It's brand new — I have no users to point to yet. You'd be early, and I'd genuinely like the feedback. Happy to answer anything.

The confirmation-before-write flow feels genuinely protective instead of annoying, especially the typing-the-project-ID step for prod. Also nice that backups happen automatically so restoring after a bad import is just a diff and a click.

the confirm-backup-execute pipeline actually being enforced in the main process is genuinely smart, felt way safer than the browser console hacks i've been doing for months

the "type the project ID to confirm" thing is genuinely smart, like it actually respects how scary a prod write is. combined with diff preview restore, this feels built by people who have fat-fingered a delete at 2am.

The backup and audit log combo is a really smart angle, especially for production work. One thing that would make this a daily driver for me: a saved query view for the JS console, so I can keep my most used filter or update scripts in a sidebar and rerun them with a quick shortcut. Right now I'd be digging through history every time.