Skip to content
Monghoul

v1.14.1 · 38 MB installer

System requirements

The one that catches people is the server version, so it is first. The platform table is the same one in the app's own README.

MongoDB server

MongoDB 4.4 or newer. Monghoul refuses to open a connection to an older server and says so, rather than connecting and failing in unclear ways later. Several features here depend on commands that 4.2 does not have.

This covers self-hosted deployments, replica sets, sharded clusters, and MongoDB Atlas.

Operating system

PlatformMinimumArchitectures
Windows x64Windows 10.exe, .msi
macOS, Apple silicon or IntelmacOS 11.dmg
Linux x64Ubuntu 22.04, Fedora 36, or equivalent (glibc 2.35).AppImage, .deb, .rpm

Monghoul is built with Tauri, so it uses the web view your operating system already ships rather than bundling a browser. That is why the installer is 38 MB rather than the size an Electron app of the same scope would be, and it is also why the Linux minimum is a distribution version rather than a processor.

On Linux, Monghoul stores the key for your saved connection passwords in the Secret Service, which is what gnome-keyring and kwallet provide. Most desktop installs already run one. Without it the passwords are still encrypted, but with a weaker key derived from Monghoul's own data, and Settings says so. macOS and Windows use the Keychain and Credential Manager, which are always present.

Disk

The installer is 38 MB. Beyond that, Monghoul stores your connection profiles, tabs, query history and themes in a local SQLite database, which grows with how much you keep rather than with the app.

A result set is virtualized, so the number of documents you can scroll through is not limited by how many fit in memory at once.

Network

Monghoul makes outbound connections to four places:

Your queries, your documents and your connection strings are not in that list and are never sent anywhere. A failed licence check does not remove access you already have, so a machine that is offline for an afternoon, or a week, keeps working. Pro does need to reach the licence server once every 30 days: an install that has not confirmed its licence for longer than that steps back to the free tier until it connects again, and one connection restarts the 30 days. The free tier has no such check and never expires.

If your cluster is only reachable from inside a network, the built-in SSH tunnel usually removes the need for a VPN. See Connect to a cluster.

What it does not need