// the find
feigeCode/navop
A native, all-in-one workspace for databases, SSH, SFTP, terminals, remote desktop, monitoring, and AI.
Navop is a native Rust desktop app built on GPUI that puts database clients, SSH and SFTP, local and remote terminals, RDP and VNC, port forwarding, server monitoring, Markdown notes, and AI agent integration into one window. It suits people who currently run a database GUI, a terminal, FileZilla, and a remote desktop client side by side and would rather have one process hold all of them.
Rendering goes through GPUI with no WebView, so this is a single native binary rather than an Electron-style shell, and the SSH, SFTP, and SQL tabs share one window and one connection store. The SSH layer is more careful than most: host-key change warnings show explicit fingerprints, a Known Hosts page lets you review and remove keys, and local, remote, and dynamic SOCKS forwarding can be saved and reused. The extension boundary is real, with database drivers, RDP providers, and importers shipped from a separate navop-extensions repo instead of bloating the core. The public MCP server gates agent access behind Safe, Confirm, and Auto permission profiles and keeps audit records, which is a more deliberate answer to letting an agent touch live servers than most AI integrations give.
The badge wall lists more than thirty databases and protocols, and the README does not say how deep any of the long tail goes. Expect MySQL, PostgreSQL, SSH, and SFTP to get the attention, and expect the Dameng, KingbaseES, GBase, Oscar, and IoTDB drivers to be thinner, with no published test matrix to check against. Encrypted sync of credentials across devices is a serious trust decision, and the README gives no description of the key model, so you would need to read the code before putting production passwords into it. The license is Apache-2.0 plus a supplementary license that bans paid distribution and competing services, so it is source-available rather than open source in the usual sense for anyone who wants to ship a derivative commercially. The Windows RDP path depends on a C++ host embedding the Microsoft RDP ActiveX control, which is a second maintenance surface beside the pure-Rust IronRDP backend.