Your SQL client is a relic. Here's what a DuckDB-native IDE looks like

Lorenço — Mon, 30 Mar 2026 02:34:18 +0000

Most of us are still using database tools that were designed for a different era.

TablePlus. DBeaver. Beekeeper Studio. Great tools. I've used all of them. But they share the same mental model: connect to a database, run a query, browse some rows. Repeat.

That model made sense when your data lived in a single Postgres or MySQL instance. It doesn't map well to how modern data work actually happens.

Today you're querying Parquet files directly. Local CSVs. S3 buckets. Remote HTTP endpoints. You're writing Python alongside SQL. You're building analyses that need version control, reproducibility, and AI assistance — not just a results grid.

The old tools bolted some of this on. DuckDB as one connection type among twenty. An "AI shell" that suggests SQL. Export to CSV. Done.

That's not wrong. It's just not enough.

I built Ruddy because DuckDB deserves to be the center of the experience, not a checkbox.

Ruddy is a macOS-native IDE where DuckDB isn't a plugin — it's the engine everything is built on.

What that looks like in practice:

No WASM, no Electron

The native DuckDB binary runs directly on your Mac. Full performance, full extension support, no browser sandbox overhead.

Notebooks are first-class

Powered by Marimo, with Python + SQL in the same environment and installable native libraries. Not a cell runner bolted on top — a real analysis environment.

An AI agent that actually executes

Ruddynie doesn't just suggest SQL. She runs queries, builds notebooks, and connects to MCP servers. You bring your own model — Claude, Gemini, OpenAI, OpenRouter.

Spatial out of the box

Geospatial data renders as maps without configuration. DuckDB's spatial extension is fully exposed.

Git built in

Your SQL and notebooks are code. They live in your repo, with version control inside the editor.

Visual query builder via ERD

Click together joins from the schema diagram. Useful for exploration and for teammates who don't live in SQL.

The old tools aren't going away, and they shouldn't. If you need a universal client for Postgres, MySQL, and fifteen other databases, they serve that well.

But if DuckDB is central to how you work — local files, analytical queries, Python notebooks, AI-assisted analysis — you deserve a tool built for that workflow from the ground up.

That's Ruddy.

→ ruddy.pro — macOS, 7-day free trial. Early-access pricing, $15 one-time or $1.25/month.

Hi I'm Ruddy

Lorenço — Sat, 28 Mar 2026 15:34:41 +0000

Most DuckDB tooling falls into one of three buckets: a browser-based WASM tool
with all the overhead that implies, a thin SQL console bolted onto the engine,
or a Python notebook that happens to use DuckDB on the side.

I wanted something different — a proper Mac app that runs the native DuckDB
binary, feels at home on macOS, and handles the full data workflow without
switching tools.

That's Ruddy.

What it does

Native DuckDB engine

No WASM. No middleware. The real binary, running locally. This matters for
performance on larger files and for features that WASM builds don't fully expose.

Notebooks powered by Marimo

Python + SQL notebooks with installable native libraries. Not a dumbed-down
cell runner — you can build full analyses and share them.

AI agent — Ruddynie

An agent that runs queries, builds notebooks, and connects to MCP servers.
Bring your own model: Claude, Gemini, OpenAI, or OpenRouter.

Visual query builder

Built on top of the ERD view — you can click together joins without writing SQL.
Useful for exploration and for less SQL-fluent teammates.

Spatial support

Geospatial data renders as maps out of the box, powered by DuckDB's spatial
extension.

Git integration

Version control built into the editor. SQL and notebook files are first-class
citizens in your repo.

Catalog + ERD

Clean schema browser with auto-generated entity-relationship diagrams.

What it connects to

Local files (Parquet, CSV, JSON), cloud data sources, and remote HTTP endpoints.
DuckDB's httpfs and S3 support is exposed natively.

Pricing

Early-access pricing while we're still in this phase, 7-day free trial:

$1.25/month — all features, auto-renewal
$7.50 — 6 months upfront
$15 one-time — pay once, use forever

Why macOS-native

DuckDB is fast. Running it inside a browser sandbox or an Electron shell adds
latency and limits what you can do with native libraries, memory management,
and OS integration. A native Mac app lets the engine breathe.

Download and try it: ruddy.pro

Happy to answer questions about the stack, the product, or how the
AI agent is architected.

DEV Community: Lorenço