LakeDB David Lago
winget install --id=DavidLago.LakeDB -e LakeDB is a fast, focused desktop client for MySQL and MariaDB on macOS, Windows, and Linux.
winget install --id=DavidLago.LakeDB -e LakeDB is a fast, focused desktop client for MySQL and MariaDB on macOS, Windows, and Linux.
A local-first database client for people tired of switching tools, losing context between connections, and trusting black-box AI with SQL. MySQL, MariaDB, PostgreSQL and SQLite in one honest, engine-aware workspace. Review generated or corrected SQL before anything runs, and stay in control of every database operation.
PostgreSQL joins LakeDB natively. Connect, explore, edit, design, export, operate and use review-first AI with PostgreSQL-specific behavior.
> 💡 Help shape LakeDB: suggest features, describe real database workflows and > react to and discuss community ideas in GitHub Discussions.
LakeDB is free to use, but it is not open source. This public repository hosts official builds, documentation, issue tracking and community feedback.
brew tap DavLagoHern/lakedb
brew trust DavLagoHern/lakedb
brew install --cask lakedb
The LakeDB tap checks the latest verified release every six hours and keeps the Cask version and SHA-256 current automatically.
| Platform | Alternative package | Install |
|---|---|---|
| macOS Apple Silicon | ZIP | Move LakeDB.app to Applications. |
| Windows x64 | Portable EXE | Run without installation. |
| Linux x64 | Debian package | Install with your package manager. |
> Public beta signing: macOS Apple Silicon packages are Developer ID signed > and notarized by Apple. Windows packages are not yet signed with a trusted > certificate. Download only from the official LakeDB repositories. Every > package has a matching SHA-256 file on the > Beta 6.1 release page.
LakeDB is currently available as Beta 6.1. See its changes and the full version history in GitHub Releases.
AI joins the existing LakeDB workflow; it does not replace it.
| Area | Available now |
|---|---|
| Connections | Multiple simultaneous MySQL, MariaDB, PostgreSQL and SQLite connections, folders, colors, read-only mode, diagnostics and search. MySQL, MariaDB and PostgreSQL support direct, SSH and TLS paths. |
| Workspaces | Independent SQL, QuerIA and table tabs per connection, with restored editor content, selected schema and layout. |
| Schema context | Browse PostgreSQL databases, schemas, search_path, tables, views, materialized views, functions, procedures, sequences and types. MySQL/MariaDB system schemas and visual relationship maps remain available. |
| SQL editor | Monaco Editor, proactive schema completion, aliases, columns, PK/index hints, local syntax diagnostics, safe quick fixes, optional AI correction, formatting, Explain, transactions, history and streaming exports. |
| QuerIA | Reusable per-connection business contexts, Normal and Agentic generation, cross-database relationships, index inspection, EXPLAIN review, visible SQL and explicit local execution. |
| Results and data | Local query-result filters, draggable result columns, virtualized table grids, pagination, search, sorting and typed safe editing with conflict checks and rollback. |
| Database tools | PostgreSQL schema backup/restore, comparison and transactional table copy; MySQL/MariaDB backup, restore, comparison and migration. Capability-aware controls stay disabled when an engine does not support them. |
| Access management | Inspect PostgreSQL roles or MySQL/MariaDB accounts and grants, then review SQL before applying supported role, password and privilege changes. |
| Safety | Local encrypted credentials, production confirmations, renderer sandboxing, read-only enforcement and no remote database execution. |
| Resilience | Stable device identity, crash recovery, session restore, verified updates, configuration backup and diagnostics. |
Shared capabilities such as merely opening multiple connections, SSH/SSL, normal autocomplete and editable grids are intentionally omitted. LakeDB's two-level connection workspace is included because every top-level connection keeps its own nested SQL, QuerIA and object tabs instead of sharing one editor context.
✓ Included · ◐ Limited, paid or a different workflow · × No comparable built-in workflow · — No built-in AI / not applicable
| Focused capability | LakeDB | DBeaver | TablePlus | MySQL Workbench | HeidiSQL |
|---|---|---|---|---|---|
| Local syntax diagnostics before execution | ✓ | ✓ | × | ◐ | × |
| Explicit AI error correction with complete SQL review | ✓ | ◐ | ◐ | — | — |
| Top-level connection tabs with isolated, restored inner workspaces | ✓ | ◐ | ✓ | ✓ | ◐ |
| PK and index-aware completion predicates | ✓ | ◐ | × | × | × |
| Typed staged edits with conflict checks and rollback | ✓ | ◐ | ◐ | ◐ | ◐ |
| Guided restore with automatic recovery dump | ✓ | ◐ | ◐ | ◐ | ◐ |
| Schema compare and generated migration plan | ✓ | ◐ | × | ✓ | × |
| Dedicated line-based natural-language documents | ✓ | × | × | — | — |
| Agentic cross-database relationship discovery | ✓ | ◐ | × | — | — |
| Mandatory local SQL review before execution | ✓ | ◐ | ◐ | — | — |
| AI never receives row data or query results | ✓ | ◐ | ✓ | — | — |
| No retained questions, generated SQL or schema names | ✓ | × | ◐ | — | — |
A partial mark includes paid editions, plug-ins or a materially different workflow. Sources: DBeaver documentation, TablePlus documentation, MySQL Workbench manual and HeidiSQL documentation.
| Stage | Direction |
|---|---|
| SQL foundation | Independent workspaces, schema-aware editing, safe data operations, database tools and recovery. |
| Beta 3 | Natural-language query documents, visible SQL and explicit local execution. |
| Beta 4 — complete | Reusable connection context, Normal and Agentic generation, cross-database relationships, index inspection, reversible opt-in and clearer execution feedback. |
| Beta 5 — complete | SQLite, local diagnostics, visible relationships, system schemas and reviewable access management. |
| Beta 6 — current | Native PostgreSQL connections, metadata, editing, design, exports, operations, database tools and review-first AI. |
| 1.0 direction | Measured quality, trusted signing and distribution, compatibility validation and complete product polish. |
Roadmap items describe direction, not a fixed release date. See ROADMAP.md for the complete quality and trust gates.
LakeDB's complete local SQL client is free to use. An optional Patreon membership helps fund its continued development and includes higher QuerIA AI usage limits. Core local database features are not locked behind a membership.
Testing, reporting and sharing LakeDB remain valuable ways to help this beta, whether or not you become a paid member.
SQL when you want it. Natural language when you need it.