lakekeeper/lakekeeper
Apache Iceberg REST Catalog in Rust — access control, credential vending and audit for every engine and AI agent. Apache 2.0. observed · 2026-08-28
Health v2 · maintenance only
91/100
- Activity 99
- Release rhythm 98
- Longevity 62
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 12.5
- age_days: 880
- days_rel: 16
- days_push: 7
- n_releases_24m: 47
Adoption not part of the score
1426 stars · 156 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Lakekeeper is an Apache Iceberg REST Catalog implementation written in Rust that provides centralized access control, credential vending, and auditing for data lakehouse engines. It lets you define permissions once in the catalog and enforce them across every compute engine (Spark, Trino, Flink, DuckDB, PyIceberg) and AI agents, powered by OpenFGA.
Use cases
- run a self-hosted Apache Iceberg REST catalog for my data lakehouse
- centralize access control across Spark, Trino, and DuckDB instead of per-engine rules
- vend storage credentials securely to query engines and AI agents
- implement RBAC or fine-grained permissions on Iceberg tables
- audit every read and write against my data lake
- govern Lance, Delta, and Parquet tables alongside Iceberg in one catalog
- integrate lakehouse permissions with Okta or Microsoft Entra ID groups
When to choose
- you need a fast, standards-compliant Iceberg REST catalog with centralized governance
- you want fine-grained access control (RBAC/ReBAC/ABAC) enforced at the catalog level for humans and AI agents
- you need credential vending and audit logging for a multi-engine lakehouse
- you prefer a Rust-native, self-hosted catalog deployable via Docker or Kubernetes
When to avoid
- you only need a lightweight single-user catalog without access control requirements
- your persistence layer cannot be Postgres (currently the only supported backend)
- you need a fully managed cloud catalog service rather than self-hosted infrastructure
Facets
service · maturity active
database auth authorization api-framework http-server search-engine monitoring secrets-management self-hosted databases big-data analytics security self-hosted apis rust self-hosted apache-iceberg iceberg-rest-catalog lakehouse data-governance credential-vending openfga rbac data-lake catalog data-engineering docker kubernetes web-server linux macos
10 sources
- readme: https://github.com/lakekeeper/lakekeeper · fetched 2026-08-28 · 7db2c81c7ddb
- homepage: https://docs.lakekeeper.io · fetched 2026-08-29 · 7d00aac0bfb8
- site_page: https://docs.lakekeeper.io/getting-started · fetched 2026-08-29 · 89a2f2d070ef
- site_page: https://docs.lakekeeper.io/docs/nightly/concepts · fetched 2026-08-29 · 4580161418db
- site_page: https://docs.lakekeeper.io/about/subscribe · fetched 2026-08-29 · 83fcabd1cdbd
- site_page: https://docs.lakekeeper.io/about/license · fetched 2026-08-29 · 082bff3466aa
- site_page: https://docs.lakekeeper.io/docs/nightly/api-overview · fetched 2026-08-29 · 6f4f78eb669e
- site_page: https://docs.lakekeeper.io/docs/nightly/api/catalog · fetched 2026-08-29 · 4235a959635d
- site_page: https://docs.lakekeeper.io/docs/nightly/api/generic-table · fetched 2026-08-29 · 8c66b9ab5c2b
- site_page: https://docs.lakekeeper.io/docs/nightly/api/management · fetched 2026-08-29 · dea5d6052fcc
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| lakekeeper/lakekeeper | main | 91 |
For agents
markdown · JSON · MCP: product_card(name="lakekeeper/lakekeeper")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem