The Query.Farm platform
A real farm is not one tool β it's fields, barns, orchards, paths, and storage working toward one outcome. Query.Farm works the same way for data access: each component does a job, and together they let teams query scattered data with SQL.
One stack, top to bottom
The components aren't six unrelated tools β they're the layers of one path a query takes. You query from a client; Haybarn or upstream DuckDB plans it; extensions add capability in-process while the VGI extension carries the query out as Arrow; Rowfence decides what the caller may see; and a worker answers from whatever it wraps. Adopt any single layer on its own β each one assumes nothing about the rest.
Query surface
SQL engine
Extension layer
Access control
Workers
Data & compute
The components, one by one
Each component does one job β connect, run, govern, package, browse, or reuse. Mix the ones you need today; the rest are ready when you grow into them.
Installable SQL capabilities
Extensions
Connect systems and add SQL capabilities.
Install connectors, transformations, sketches, scripting, geospatial, JSON, text, and operational tools without building native extension plumbing yourself.
Connector marketplace
Orchard
Discover, subscribe to, and reuse connectors.
The marketplace for VGI workers and connectors β find a connector, subscribe, and attach it from DuckDB or Haybarn with one line of SQL.
Vector Gateway Interface
VGI
Run custom or reusable workers from SQL.
Make APIs, services, models, and business logic available as SQL-accessible tables and functions through Apache Arrowβbased workers β in Python, TypeScript, Go, Rust, or Java.
Row & column security for VGI
Rowfence
Enforce row, column, and function access.
A Cedar-policy proxy that sits in front of any VGI worker and decides, on every query, which rows, columns, and functions a caller can touch β hosted or on your own infrastructure.
Independent distribution
Haybarn
Bring DuckDB into the enterprise.
Same SQL and database files as DuckDB, with faster object-store reads, signed artifacts, build provenance, curated extension defaults, and mirrorable npm / PyPI channels.
Web workspace for VGI
Cupola
Browse and query workers in the browser.
An open-source, WASM-powered web workspace for VGI: browse catalogs, run SQL, pivot data, and use a built-in AI agent β free and available now.
One data platform
These components work as one platform for building, operating, and reusing SQL-accessible connections β adopt them piece by piece. Extensions add capability, VGI runs the workers, Rowfence governs who sees what, the Orchard shares them, Haybarn ships the engine, and Cupola is where you sit down and query.
Ship with what's ready now
Three production-ready components you can adopt immediately β independently or together.
DuckDB Extensions
Installable SQL capabilities
Specialized extensions for connectors, transformations, sketches, scripting, and more.
- Connectors, transformations, sketches, and scripting
- All open source
- Production-ready today
VGI
Vector Gateway Interface
Extend DuckDB with functionality in Python, TypeScript, Go, Rust, or Java. Apache Arrow is the cross-language glue β no FFI, no rebuilds, no version locking.
- DuckDB-side extension + Python function framework
- SDKs for Python, TypeScript, Go, Rust, and Java
- Apache Arrow IPC over pipes, sockets, or HTTP
Haybarn
An independent distribution of DuckDB
The DuckDB source, rebuilt as branded binaries with an independent release cadence and a signed extension ecosystem. ABI- and file-format-compatible with upstream DuckDB.
- Independent release cadence and versioning
- Signed extensions, SLSA build provenance
- Install via npx, uvx, pip, or direct download
Need something custom?
We build DuckDB extensions for clients who need specific functionality β from connectors to compute engines.