DuckDB your team can ship.
Same SQL and database files, plus reviewable releases, rebuilt extensions, and artifacts your team can verify.
What Haybarn adds
Drop-in compatibility
Same SQL, APIs, files, and extension names.
Verified artifacts
Engine and extensions can be checked before use.
Concrete install paths
Install through npm, PyPI, and GitHub Releases.
Safer defaults
Third-party vendor extensions stay opt-in.
Why Haybarn
The production layer around DuckDB
DuckDB is an excellent engine. Haybarn adds the distribution, signing, extension, and release controls teams need when DuckDB becomes part of an app, service, agent, or regulated workflow.
Approve it
Signatures, checksums, and build history give security teams something concrete to review.
Mirror it
Artifacts and extensions are published through channels that fit internal registries and controlled environments.
Ship it
Use familiar DuckDB SQL and extension commands while Haybarn handles the production release layer.
Drop-in where it matters
Adopt the distribution without rewriting the work.
Same SQL
Queries behave like DuckDB.
Same files
.duckdb files stay compatible with DuckDB v1.5.3.
Same extension commands
INSTALL and LOAD keep the familiar shape.
One-line Python path
Use import haybarn as duckdb when the library package is live.
Try it
A familiar extension command, a verified artifact behind it
Haybarn keeps the DuckDB workflow familiar while changing how the binary is built, signed, published, and tracked.
# uvx fetches and runs the Haybarn CLI temporarily.
uvx haybarn-cli==1.5.3rc1
# Or use npx:
# npx haybarn@rc
# Same DuckDB engine and SQL.
memory H SELECT version();
# h3 is a DuckDB community extension for H3 geospatial indexing.
# The command is familiar; Haybarn resolves it from Haybarn's
# rebuilt and signed extension channel.
memory H INSTALL h3 FROM community;
memory H LOAD h3;
memory H SELECT h3_latlng_to_cell(37.7887, -122.3931, 9);
This is the point: h3 is a normal DuckDB community extension, but Haybarn rebuilds it for the Haybarn engine, verifies it with the Haybarn key, and tracks whether it is ready for the release.
Signed extension ecosystem
Extensions, ready to load
Haybarn rebuilds DuckDB extensions, signs them, and tracks whether they are ready for each release.
Same names
Use familiar INSTALL and LOAD commands.
Core included
Common capabilities ship with the engine.
Community rebuilt
Community extensions are signed and published by Haybarn.
For production teams
Haybarn's extension distribution is designed for approval and repeatability: verifiable binaries, immutable hosted artifacts, release status, and package paths that fit npm/PyPI-style dependency workflows.
Expert help
Running Haybarn in production?
We help teams adopt Haybarn: packaging, signing, internal mirrors, extension portability, and integration with existing DuckDB-based pipelines.
Haybarn is not affiliated with, sponsored by, or endorsed by the DuckDB Foundation or DuckDB Labs. DuckDB is a trademark of the DuckDB Foundation. Haybarn is published by Query Farm LLC and distributed under the MIT License.