# duckdb/ducklake

DuckLake is an integrated data lake and catalog format

Repository: https://github.com/duckdb/ducklake
Canonical: https://ross.abutalabs.com/products/ducklake
Homepage: https://ducklake.select
Language: C++
License: MIT
License Family: permissive
Last push: 2026-08-26T10:56:00+00:00

## Health v2 (maintenance only)
Score: 65/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 35, longevity 39
- inputs: {"age_days": 548, "days_push": 7, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases, no_readme
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2939, forks 240 (observed 2026-08-28T04:07:30.944443+00:00)

## What it is
DuckLake is an integrated data lake and lakehouse catalog format that stores data as Parquet files and manages metadata in an ACID-compliant SQL database such as DuckDB, SQLite, or PostgreSQL. It ships as a DuckDB extension providing snapshots, time travel, schema evolution, partitioning, and multi-client concurrent access.

## Use cases
- build a lakehouse with a SQL-based catalog
- run time travel queries on a data lake
- share a dataset across multiple DuckDB instances with concurrent writes
- replace a single large DuckDB file with partitioned Parquet storage
- migrate from DuckDB files or Iceberg to a simpler lakehouse format
- store data lake files in object storage with ACID guarantees

## When to choose
- you want lakehouse features like snapshots, schema evolution, and ACID transactions without Iceberg/Delta complexity
- you already use DuckDB and need multiplayer concurrent access to shared data
- you prefer a SQL database as the catalog with no vendor lock-in

## When to avoid
- you need a catalog server independent of SQL databases or non-SQL catalog ecosystems
- your stack is Spark-centric with deep Iceberg/Delta Lake tooling integrations
- you only need a single-user embedded database with no lake requirements

## Facets
- artifact type: library
- maturity: active
- function: database, etl, analytics
- domain: databases, big-data, analytics
- platform: cpp, python, cli, cross-platform, self-hosted
- tags: lakehouse-format, open-table-format, parquet, duckdb-extension, data-lake, acid-transactions, time-travel, schema-evolution, catalog, data-engineering

## Member repositories
- duckdb/ducklake (main) score 65

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:07:30.944443+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T07:32:58.161366+00:00, confidence not recorded.
  - homepage: https://ducklake.select (fetched 2026-08-29T09:48:20.638782+00:00, sha ab4288786ab2)
  - site_page: https://ducklake.select/docs/stable (fetched 2026-08-29T09:48:20.641668+00:00, sha 68d761e49426)
  - site_page: https://ducklake.select/docs/stable/specification/introduction (fetched 2026-08-29T09:48:20.643770+00:00, sha cd70d6d02886)
  - site_page: https://ducklake.select/docs/stable/duckdb/introduction (fetched 2026-08-29T09:48:20.645741+00:00, sha f1ff45b332d0)
  - site_page: https://ducklake.select/docs/stable/duckdb/introduction.html (fetched 2026-08-29T09:48:20.650420+00:00, sha f5b6e907feac)
  - site_page: https://ducklake.select/docs/stable/specification/introduction.html (fetched 2026-08-29T09:48:20.654870+00:00, sha 8f6b89b51d77)
  - site_page: https://ducklake.select/faq (fetched 2026-08-29T09:48:20.647917+00:00, sha 9ff25b5763d4)
  - site_page: https://ducklake.select/faq.html (fetched 2026-08-29T09:48:20.652805+00:00, sha 68354fee3b76)
- Data as of 2026-08-30T08:39:29.467469+00:00.