Hugr Lab builds open DuckDB extensions for the systems companies already run, and the pieces that make DuckDB safe to use across a company. Built in Germany, in the open.
In August 2026 AWS agreed to acquire DuckLabs, the team behind DuckDB. DuckDB itself stays open source. Companies in Europe that adopt it still need it to fit their systems, their identity providers and their auditors, from a vendor under EU jurisdiction. That is what Hugr Lab works on.
Each product works on its own and installs in minutes. Open source at the core; run it yourself or let us run it in your cloud.
One sign-in through your identity provider, and every analyst and application gets exactly the credentials their role allows. Rotate and revoke centrally, or keep secrets in the vault you already have.
About tresorQuery and load SQL Server, Azure SQL and Fabric from DuckDB over the native protocol. Keep a DuckLake catalog in SQL Server.
About the SQL Server extensionsThe GraphQL engine you may know from hugr-lab.github.io. One API over databases, files and services.
About hugr classicEverything we ship runs on your machines or in your own cloud tenant. Nothing is copied to us.
Our extensions are open source (MIT, Apache-2.0); the few commercial parts are source-available. You can read everything you run.
Hugr Lab is based in Germany. Azure first, with Open Telekom Cloud and STACKIT next.
We publish how our extensions work and how fast they are. Start with SQL Server: two lines in DuckDB.
Data engineering in short projects: SQL Server into a lakehouse, DuckDB in front of your BI, or a platform that stays in your cloud. Done by the people who wrote the code.
Hugr Lab UG is being founded. We take on projects from November 2026.