Start here
Query it
Explore from a browser workspace or bring a production-ready DuckDB distribution to the tools your team already uses.
Open-source connectivity for the modern query stack
Turn APIs, services, databases, and custom code into tables and functions using DuckDB today.
Choose a starting point
Start with the outcome. Each path shows the products that can get you there today.
Start here
Explore from a browser workspace or bring a production-ready DuckDB distribution to the tools your team already uses.
Add capability
Install a DuckDB extension or turn an API, service, model, or piece of custom code into a table or function with VGI.
Share safely
Apply policy when it is needed, then publish reusable workers so other people and agents can reach the same capability.
The product map
Follow a question from the person or agent asking it, through the query engine and integration layer, to the worker and source that can answer it.
Start with the stubborn thing
In thirty minutes, we can place it on the map, tell you what already exists, and scope the smallest useful next step. No deck, and no platform prerequisite.
From the blog
Release notes, product thinking, and technical work from Query.Farm.
The IP is safe under the DuckDB Foundation, but the Foundation doesn't cut releases — DuckLabs does. What the AWS acquisition changes for people who build on DuckDB, and what Query Farm is doing about it.
Every DuckDB engine release needs its community extensions rebuilt before they install. With data from 1,400+ PRs and a full-catalogue rebuild, we make the case for treating the catalogue as a distribution — and show Haybarn rebuilds it ~2.4× faster.
A DuckDB extension that compiles for WebAssembly has only proven that it compiles. Whether it loads, and whether it actually runs, are separate questions. I built a Node harness to ask them across 124 community extensions. Here's what it found and the fixes that came out of it.