New Support Policy for DuckDB

DuckDB Labs is announcing a new support policy for DuckDB and our new flexible commercial support option.

We are absolutely thrilled how much the DuckDB community has grown, from student projects to enterprise integrations. There are now millions of downloads each month and large growth in the Discord server, Twitter followers, GitHub stars and so forth. When we started DuckDB back in 2018, we could have not imagined this level of adoption and we are absolutely humbled to see it.

There are some drawbacks to having a large amount of users. The DuckDB project and the company behind the project, DuckDB Labs, are not funded by venture capital by our own choice. We feel investment would force the project direction towards monetization, and we would much prefer keeping DuckDB open and available for as many people as possible. This means that our team cannot grow at the same pace as DuckDB’s usage. This means we have to make some hard choices on how to prioritize our time.

We would like to be upfront and clarify DuckDB’s support model, and the following policies apply to our free support:

  • Users can file bug reports as issues on GitHub and suggests features on GitHub Discussions.
  • There is no guarantee w.r.t. response time to the reports nor is there any guarantee that issues will be resolved (e.g., fixed) within any time frame.
  • We are also unable to support a large volume of support requests from individuals or teams working in the same company.
  • We only support the C, Java (JDBC), ODBC, Node.JS, Python and R client APIs as well as the command line shell. The C++ API is intended for internal use and is not designed as a stable user-facing API. The Julia and Swift APIs are rather experimental and not supported.
  • Within the main project, the community support policy only covers the the httpfs, icu, json and parquet extensions. The autocomplete, excel, fts, inet, sqlsmith, tpcds and tpch extensions are not supported.
  • We are unable to answer questions about DuckDB internals, e.g., physical operators or storage internals. In general, if an issue cannot be triggered from SQL or one of the supported client APIs, it’s probably out of scope.
  • We are unable to answer questions regarding all repositories under the duckdb organization, only duckdb/duckdb, duckdb/duckdb-java, duckdb/duckdb-r, and duckdb/duckdb-node are in scope.
  • In general, issues that cause crashes (segfault, bus error, abort) and issues that result in internal errors get higher priority.
  • We can only support the following platforms: Windows 10+ on x86_64, macOS latest, Linux x86_64 & aarch64, mainstream distributions under support by distributor running with glibc. The last three Ubuntu LTS releases are a safe bet (currently: Ubuntu 20.04, 22.04 and 24.04).
  • We only support the latest stable version and the bleeding edge version (main branch) of DuckDB.
  • We do not support big-endian architectures.
  • Debug builds of DuckDB’s clients and tooling are out of scope.
  • Users are welcome to join our Discord server to engage with the DuckDB community.

For support requests that fall outside this support policy, we recommend contacting DuckDB Labs for commercial support options. Commercial support contracts come with guaranteed response time, private issue tracker and private datasets, larger support volume and extended scope with regards to components.

There are several ways that you can help us resolve issues more quickly. The more time you can spend to reduce our team’s workload regarding the issue, the more likely we can help. We sometimes spend an enormous amount of time divining missing information in bug reports like schema, datasets, previous state, environment, etc.

  • Please (please) follow the issue template.
  • Please make every effort to provide the data that is triggering the issue. The template advises to include all of the required data in your issue itself. Sometimes this means actually creating a dataset that you can share, which is preferably minimal in size. If you can only reproduce the issue on a proprietary data set, DuckDB Labs offers commercial support where this is possible. We are not able to use proprietary data in the free support tier in general.
  • If possible, include test cases that succeed that are similar to the failure to help pinpoint the problem.
  • Try to replicate the issue in multiple clients (CLI preferred).
  • Debugging issues is a fantastic way to contribute to DuckDB!
  • Providing background information about why you are approaching your task the way you are can help DuckDB Labs suggest workarounds prior to a fix.

We would like to thank our awesome community and partners in joining us in the journey so far. We are looking forward to continuing our collaboration and delivering new releases DuckDB for everyone to use.

back to main page