Overview

(Last Updated: April 2026)

The DuckLake project is governed by the non-profit DuckDB Foundation. The Foundation and DuckDB Labs are not funded by external investors (e.g., venture capital). Instead, the Foundation is funded by contributions from its members, while DuckDB Labs' revenue is based on commercial support and feature prioritization services. These extend to the ducklake DuckDB extension.

Planned Features

This section lists the features that we plan to work on for future DuckLake releases. The list was compiled by the DuckLake maintainers and is based on the long-term vision for the project and general interactions with users in the open-source community.

• Inlining for the VARIANT type.
• Multi-deletion vector Puffin files.

Please note that there are no guarantees that a particular feature will be released within the next release. Everything on this page is subject to change without notice.

Future Work / Looking for Funding

These are some of the items that we plan to support in the future. If you are interested in prioritizing some of this work, get in touch with DuckDB Labs.

• User-defined types.
• Role-based access control.
• Materialized views and incremental maintenance.
• Protected snapshots.
• Branching/merge functionality.
• Read performance improvements regarding Parquet Bloom filters and metadata scans. See issues #389 and #404.
• Allow PRIMARY KEY syntax without enforcing it, similar to what other OLAP engines do (e.g., BigQuery).
• Fixed-size arrays.
• PostgreSQL performance improvements: reduce number of roundtrips and explore optimizations for large metadata (e.g., by using stored producedures).
• MySQL robustness improvements.