Open-source connectivity for the modern query stack
Turn APIs, services, databases, and custom code into tables and functions. Start with DuckDB today; VGI is expanding the same model to DataFusion, Trino, Spark, SQLite, and Polars.
The product map
See the whole system at once
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
Bring us the data, API, or code your team cannot query cleanly.
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
Latest updates
Release notes, product thinking, and technical work from Query.Farm.
The Foundation owns the IP. DuckLabs ships the release.
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.
Building DuckDB's Community Extensions, Faster and More Consistently
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.
Compiling Isn't Running: Functionally Testing DuckDB-WASM Extensions
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.