An open-source desktop database client for people who spend a lot of time in SQL.
Cellar keeps schema browsing, queries, results, and pending data changes in one native workspace. It is keyboard-first, MIT licensed, local by default, and built in Rust with GPUI.
It is also early-access software. The useful database workflow is here, but there are still rough edges and unfinished parts.
Browse, query and edit databases inside Codex with the Cellar plugin. The Apple Silicon macOS preview is distributed through a versioned GitHub marketplace. See installation, supported workflows and limitations. The plugin has its own version and release assets, separate from the native desktop app.
Download the latest release. The signed build currently supports Apple Silicon Macs running macOS 13 or newer.
Windows and Linux builds are checked in CI, but release packaging for them is not ready yet. Cellar 0.3.5 was the final Intel Mac release.
- PostgreSQL, MySQL, SQLite, SQL Server, Azure SQL, Firestore, Convex, and Cosmos DB connections
- Supabase, Neon, and PlanetScale through their native database protocols
- Live schema browsing, SQL editing, completion, formatting, and query history
- A bounded, two-axis virtualized result grid for large tables
- Reviewable row edits that stay pending until you choose to commit them
- Query plans, schema comparison, ER diagrams, import/export, and a
Cmd/Ctrl+Kcommand palette
AI support is being built around your own provider account. Context stays visible, generated SQL stays reviewable, and Cellar does not put a hosted proxy between you and the provider.
There is no Cellar account or cloud sync. Database credentials and provider keys are stored through the operating system keychain, and telemetry is off by default.
SSH tunneling is supported for PostgreSQL/Supabase/Neon, MySQL/PlanetScale, and SQL Server. Azure SQL, SQLite, and HTTP-based drivers do not support SSH tunnels. Direct Azure SQL connections remain available; saved Azure SQL tunnel settings are rejected rather than silently connecting directly.
In the connection editor, keep General → Host / Port set to the database address as seen from the SSH server. Enable SSH tunnel, enter the SSH server's host, port and user, then choose SSH agent, Private key, or Password. Encrypted private keys support a separate passphrase.
Enable Use jump host when the SSH server is reachable only through a bastion. The jump host has its own host, port, user, authentication method and credentials; they need not match the SSH server.
For an unknown SSH server or jump host, Cellar displays its host, port, key algorithm, and SHA256 fingerprint. Verify that fingerprint with your server administrator or another independent trusted source before choosing Trust & Connect (or Trust & Test). Confirmation appends the key to ~/.ssh/known_hosts and retries; Cancel writes nothing. Jump hosts and SSH servers are confirmed separately. Existing trusted entries are reused. Changed or revoked keys remain blocked and cannot be overridden in this dialog; SSH host certificates are not supported yet. SSH-agent authentication uses your local agent; agent forwarding is not required. Passwords and key passphrases are stored in the OS keychain; blank credential fields preserve saved values, and Clear saved password / passphrase removes them on save. Secrets for an SSH hop or authentication method you no longer use are removed when you save. Test connection uses the same tunnel settings as a saved connection.
The SSL mode applies to the database connection inside the tunnel, checked against the database host from General, not the SSH server. Prefer and Require encrypt the connection but do not verify the database certificate, matching standard PostgreSQL and MySQL clients; Prefer also connects to a server without TLS. For MySQL over SSH, Prefer without server TLS still protects the password with the server's RSA key, as caching_sha2_password and sha256_password do. Use Verify CA or Verify full when the certificate must be authenticated.
Downgrade caveat: older Cellar builds ignore SSH settings and would connect directly to the database host. Do not open SSH-configured connections with an older version.
Prerequisites:
- Rust stable
- Node.js 20 or newer
- pnpm 9 or newer
- macOS users: Xcode command-line tools
git clone https://github.com/MRL-00/cellar.git
cd cellar
pnpm install
pnpm devpnpm dev runs the native GPUI desktop client. The website is a separate app and can be started with pnpm --filter @cellar/site dev.
Useful checks:
cargo check --workspace
cargo test --workspace
pnpm build
pnpm typecheck
pnpm lint
pnpm testGPUI entities and models
-> cellar-runtime services
-> cellar-core driver traits
-> concrete database drivers
The production desktop app lives in apps/desktop-gpui. Shared Rust services and database drivers live under crates, while apps/site contains the React/Vite marketing site. There is no browser runtime or second IPC layer in the desktop app.
Read SPEC.md for the product and architecture decisions, and the architecture overview for the shorter version.
Issues and pull requests are welcome. Please run the relevant checks before opening a pull request:
pnpm test
cargo check --workspace
pnpm lintUse a conventional prefix in the title, for example feat: add query templates or fix: preserve pending row edits.
