Query any data, anywhere, with SQL.
Query.Farm turns APIs, public datasets, files, databases, and custom code into SQL-accessible tables and functions. Teams can discover, reuse, and ship those connections without building a data platform from scratch.
Start with a question
What we want to answer
Where should I open a new coffee shop?
Gather the public sources needed to answer it:
a local CSV, a public API, a civic dataset, and a weather dataset. Query.Farm makes each one available to the same SQL workspace.
Hover a source to see how it flows into the query. Use the same pattern for SaaS APIs, files, models, and internal services.
Query.Farm workspace
Join live sources with ordinary SQL
ATTACH 'storefronts.csv' AS storefronts (...);
ATTACH 'transit' AS transit (...);
ATTACH 'business_permits' AS permits (...);
ATTACH 'weather' AS weather (...);
SELECT neighborhood, foot_traffic, median_rent,
nearby_cafes, rainy_days, opportunity_score
FROM storefronts.available
JOIN transit.station_activity USING (neighborhood)
JOIN permits.food_service USING (neighborhood)
JOIN weather.monthly USING (neighborhood)
ORDER BY opportunity_score DESC;Result
Joined different source types in one query
Long Island City rises to the top: strong foot traffic, manageable rent, enough rainy-day demand, and less cafe saturation than other busy neighborhoods.
Schemas discovered
Inspect tables immediately
No warehouse model
No foreign-key setup first
No ETL job
Query before moving data
No pandas glue
Join with plain SQL
The data farm
A platform of components that work together
A real farm is not one tool. It is fields, barns, orchards, paths, storage, and equipment working toward one outcome. Query.Farm works the same way for data access: each component does a job, and together they form a platform for querying scattered data with SQL.
Query.Farm data platform
Every component works together
Each square is one part of the data farm. Together they let teams build, discover, run, and reuse SQL-accessible data connections.
Extensions
Connect systems and add SQL capabilities.
VGI
Run custom or reusable workers from SQL.
Cupola
Give teams a place to browse and operate workers.
Haybarn
Package and ship the platform safely.
The Orchard
Discover and connect reusable data components.
All together
The Query.Farm platform
These components work together as one data platform for building, operating, and reusing SQL-accessible connections.
Why Query.Farm
Reusable SQL access for scattered data
Turn scattered data and code into reusable SQL components. Attach them, join them, reuse them, and ship.
The difference
Make every useful data source queryable.
Query.Farm is for teams that need access to data now, but do not want to spend months building connector infrastructure first.
Turn APIs, files, services, models, and custom code into SQL components.
Discover and reuse those components across teams and projects.
Ship data workflows without building connector infrastructure first.
Example: research data platform
A team has market feeds, vendor APIs, internal models, CSV drops, and application data. Query.Farm turns each source into a reusable SQL component so analysts, apps, and agents can join them without rebuilding connectors every time.
The point
You get the useful parts of a data platform: discovery, reusable connectors, SQL access, packaging, and production paths, without starting by building platform infrastructure.
Use cases
Access scattered data through one fast SQL layer
Attach the source. Discover the schema. Query with SQL. Reuse the result anywhere.
Query data where it lives
APIs, files, services, and databases become SQL-accessible without moving everything first.
Join sources quickly
Attach sources and join them with SQL. No pandas glue, ETL job, or warehouse model required.
Reuse connectors
Build a connector once, catalog it, and reuse it across projects.
Call code from SQL
Run models, validators, enrichment, and internal services from SQL.
Embed analytics
Bring fast SQL into apps, agents, notebooks, workflows, and internal tools.
Package for production
Ship signed builds, curated catalogs, and deployable extension packages.
Why DuckDB
Fast SQL where the work happens
DuckDB gives Query.Farm a fast, embeddable SQL engine that runs close to the workflow.
Runs anywhere
Use SQL inside an app, notebook, CLI, browser, service, or workflow.
Fast without a cluster
Great for analytical SQL near files, apps, connectors, and services.
Simple to embed
No warehouse-sized footprint when the job is local, embedded, or app-adjacent.
Expert help
Build the data access layer. Skip the platform detour.
Start with an extension, add VGI workers, evaluate Haybarn, or bring us the connector, worker, extension, or production data platform your team needs to ship.
From the Blog
Latest Updates
Release notes, product thinking, and technical notes from the Query.Farm team.
DuckDB Extension Best Practices: A Developer Guide
Learn how to build, optimize, and deploy DuckDB extensions with this comprehensive guide covering architecture, performance, and testing.
Announcing Query.Farm: DuckDB Extensions and Services
We're excited to introduce Query.Farm, a company dedicated to building the DuckDB ecosystem with extensions, services, and infrastructure tools.