Most MongoDB GUIs are very good at one thing: showing you rows. You connect, you browse a collection, you run a find. That's table stakes — and it's where most tools stop.
The hard part of running MongoDB isn't looking at documents. It's the questions that don't fit in a table view:
- Why is this query slow, and what index actually fixes it?
- Where is my storage going, and how much of it can I reclaim?
- Which of these documents are duplicates, and is it safe to delete them?
- What's quietly drifting in my schema before it breaks a query in production?
mongoui is built around those questions. Its engine runs on your machine and connects straight to your database. Full documents and MongoDB credentials are never sent to mongoui.
Scan → review → fix
The whole product is one loop. A Smart Scan runs a full health pass — indexes, storage, duplicates, schema — and tells you exactly what needs attention. Green when you're clear, specific when you're not.
From there you review: real explain() output read back in plain English,
storage broken down collection by collection, duplicate clusters grouped by the
key you define.
Then you fix — and this is the part we care most about. Every cleanup is a dry run first. You see the exact before/after counts and the blast radius before anything is written. When you do apply, it's behind a gate, and a snapshot means any change can be undone with one click.
Local-first, by design
The engine and MongoDB connection are local. Full documents and MongoDB credentials are never sent to mongoui. Optimize and Debug start in Local mode. If you explicitly choose AI narration or an AI Cleanup draft, the disclosed authored request and bounded structural context go directly to your selected provider using your key. mongoui has no AI proxy.
This blog is where we'll write about what we learn building it — query optimization, safe data maintenance, and the parts of MongoDB that don't show up in a row viewer. The docs are the place to start if you just want to get it running.