nvim-dbee
nvim-dbee is a Neovim plugin that provides an interactive database client with a Go backend and Lua frontend, allowing developers to execute SQL queries directly from their editor. It supports multiple database types, handles large result sets with pagination, and requires Neovim 0.10 or later.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | kndndrj/nvim-dbee |
| Owner | kndndrj |
| Primary language | Go |
| License | GPL-3.0 — OSI-approved |
| Stars | 1.3k |
| Forks | 93 |
| Open issues | 76 |
| Latest release | v0.1.9 (2024-07-26) |
| Last updated | 2025-07-25 |
| Source | https://github.com/kndndrj/nvim-dbee |
What nvim-dbee is
A Go-based database client plugin for Neovim (v0.10+) with a Lua UI layer built on nui.nvim. The backend uses native Go drivers without relying on CLI tools and implements an iterator pattern for efficient result handling. Installation includes automatic binary compilation or pre-built downloads from a CI pipeline targeting multiple OS/architecture combinations.
Get the nvim-dbee source
Clone the repository and explore it locally.
git clone https://github.com/kndndrj/nvim-dbee.gitcd nvim-dbee# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Automatic binary installation is attempted on plugin setup; manual installation via `go install`, curl, wget, or local build is available as fallback.
- Requires nui.nvim as a dependency; ensure it is installed and compatible with your Neovim version before setup.
- Connections are specified via configuration sources; no built-in UI for connection management beyond edit/delete operations—connection strings must be provided externally.
- Result pagination is built-in with configurable page size (default 100); large queries may require memory and network considerations depending on database size.
- Scratchpad files are stored on disk in a configurable directory; directory structure and file naming conventions should be reviewed before deployment.
When to avoid it — and what to weigh
- Require Neovim < 0.10 — This plugin explicitly requires Neovim 0.10 or later; older editor versions are not supported.
- Using non-Neovim editors — This is a Neovim-specific plugin; it does not work with Vim, VSCode, or other editors.
- Expect production-stable software — README explicitly states 'Alpha Software - Expect Breaking Changes'; major version is still 0.x with active issue backlog (76 open issues).
- Need platform support guarantees — Cross-platform support depends on Go dependency compatibility and CI pipeline success; some platforms may have missing or untested binaries.
License & commercial use
Licensed under GPL-3.0 (GNU General Public License v3.0). This is a copyleft license requiring that any distributed modifications or derivative works also be licensed under GPL-3.0.
GPL-3.0 is a copyleft open-source license. Commercial use of the unmodified plugin itself is permitted, but distributing modified versions or bundling the plugin into proprietary software requires those works to also be GPL-3.0 licensed. Internal business use without distribution is not restricted. Requires legal review if integration into a commercial product with proprietary modifications is planned.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Possible |
| Assessment confidence | Medium |
Connection strings and credentials are configured via sources specified in setup; storage mechanism (file, environment, etc.) is not detailed in the excerpt. No explicit mention of credential encryption, connection pooling security, or TLS/SSL options. Database query execution is sandboxed within Neovim but relies on the underlying database driver security. Requires review of connection source handling and database driver documentation for production use.
Alternatives to consider
vim-dadbod (with vim-dadbod-ui)
Mature Vim/Neovim database plugin using `vim-dadbod` as backend; simpler, battle-tested but less feature-rich than nvim-dbee.
DBeaver
Standalone full-featured database IDE with schema exploration, query building, and admin tools; not editor-integrated but more comprehensive for advanced DBA tasks.
DataGrip (JetBrains)
IDE-integrated database client with advanced debugging, refactoring, and analysis; commercial but offers broader language and tool integration than editor plugins.
Build on nvim-dbee with DEV.co software developers
Use Devco's engineering expertise to integrate nvim-dbee or evaluate alternative database clients for your team's Neovim setup and ensure secure, production-ready database interactions.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
nvim-dbee FAQ
Does nvim-dbee support my database?
Can I use nvim-dbee in a team or CI/CD pipeline?
What happens if my database query returns millions of rows?
Is the GPL-3.0 license compatible with my closed-source project?
Custom software development services
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If nvim-dbee is part of your open-source databases roadmap, our team can implement, customize, migrate, and maintain it.
Integrate nvim-dbee Into Your Development Workflow
Use Devco's engineering expertise to integrate nvim-dbee or evaluate alternative database clients for your team's Neovim setup and ensure secure, production-ready database interactions.