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.
Crossfield · Coming in Haybarn
Give teams and AI agents shared reporting definitions through Crossfield, Query Farm’s semantic layer inside DuckDB. Inspect calculations, combine models and compare revisions in one connection.
Built around supported Apache Ossie definitions, with reporting rules checked inside the query engine. Explore fulfillment and investment examples with source data, models and answers you can verify.
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.
We compare issue activity and first-time reporters across 46 DuckDB-owned repositories to assess upgrading to 2.0 or waiting for 2.0.1.
Query Farm now distributes its DuckDB 2.0 extensions through its own repository. Here's how to install them and why we're changing how we deliver releases.
Haybarn-Wasm, a drop-in fork of DuckDB-Wasm, loads five extensions in 1.9 seconds, against 5.4 for upstream. Here's where the startup time went and how we cut it.