We are continuously amazed by the growth of the DuckDB community. There are now 10M+ downloads each month and a large amount of social media 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 to keep 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:
+ +-
+
- Where to file tickets: Users can file bug reports as issues on GitHub and suggest features on GitHub Discussions. +
- Response time: We attempt to reproduce incoming issues within a few business days. Internally, we assign issues in weekly batches. However, we are unable to guarantee that issues will be resolved (e.g., fixed) within any time frame. +
- Volume: We are also unable to support a large volume of support requests from individuals or teams working in the same company. +
- APIs: We only support the C, Java (JDBC), ODBC, Node.JS (Neo), 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. Other APIs such as Julia and Swift APIs are rather experimental and not supported. See the Client overview page for more details. +
- Extensions: Within the main project, the community support policy only covers the httpfs, icu, json and parquet extensions. Other extensions, such as autocomplete, excel, fts, inet, tpcds, tpch, etc., are not supported. +
- Internals: 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. +
- Crashes and internal errors: Issues that cause crashes (segfault, bus error, abort) and issues that result in internal errors get higher priority. +
- Platforms: We 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). +
- Versions: We only support the latest stable version and the bleeding edge version (
mainbranch) of DuckDB.
+ - Architectures: We do not support 32-bit and big-endian architectures. +
- Debug builds: Debug builds of DuckDB’s clients and tooling are out of scope. +
- Discord: Users are welcome to join our Discord server to engage with the DuckDB community. +
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.
+ +-
+
- Issue template: Please (please) follow the issue template. +
- Data sharing: 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. +
- Succeeding examples: If possible, include test cases that succeed that are similar to the failure to help pinpoint the problem. +
- Multiple clients: Try to replicate the issue in multiple clients (CLI preferred). +
- Debugging issues: Debugging issues is a fantastic way to contribute to DuckDB! +
- Background information: 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.
+ +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.
+ +
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+ 
+