The story of Mingo — the MongoDB browser

Radoslav Toth
2 min readJan 27, 2020


As a NodeJS developer, heavily using MongoDB for my projects, I have long dreamed of a better MongoDB admin.

Existing solutions lacked usability and features to make browsing and querying documents enjoyable. They would easily analyse data, list documents and build aggregations, but they felt awkward with simple everyday tasks. I mean, simple things, such as finding a document quickly, viewing its content in a nice layout or doing common actions with one click.

Well, dreaming only gets you so far…

…so we started building our own app.

Today, we are proudly announcing the official v1 release of Mingo.

We love it. We use it daily and it saves us TIME. Mingo feels like what multi-cursor felt like back then. Remember?

Our aim was to build a good-looking app that works intuitively, learns as you use it and gets to results with minimum clicks.

So, we created a browser. A MongoDB browser. A browser that feels and works just like a regular browser, with tabs, address bar and keyboard shortcuts we use so much.

What is so great about it?

Besides query autocomplete, inline edit, table+tree view and other neat features, Mingo recognises foreign keys and finds the document for you with one click.

Also, a string-like query will be searched in all indexed fields. Thus, a query “shirt” will search for all documents with any indexed field matching “shirt”. This makes querying a lot faster than any autocomplete!

Forget dates in queries. They are a big mess :-).
Try {createdAt: #today} or {createdAt: #last3days} instead!

This is just to give a few examples. Mingo’s Aggregator, Data structure analyzer or Compare & Sync will require separate articles to describe. There’s an extensive list of features on our website.

Give it a try!

You have to try Mingo to get the full picture. Download is available at

We need your feedback

Please, let us know what you think. If you have any ideas, bugs or a cool feature you would appreciate, submit an issue at our GitHub repository.

Thank you!