Lakekeeper
PulseGate's liveness check found it on 11 Sep 2026; it is registered on GitHub and has been in the index since 11 Sep 2026. How this is checked
Lakekeeper is an Apache Iceberg REST Catalog that applies access policies to data requests from people, applications, analytics engines, and AI agents. It supports credential vending, audit trails, air-gapped deployment, and integrations with cloud storage and data platforms.
Inferred · not functionally tested
Overview
6 featuresPurpose: Controlling and auditing access to data across analytics engines, applications, and AI agents.
Inferred · not functionally tested
Audience: data platform, security, and compliance teams
Inferred · not functionally tested
Functions: monitoring
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: unknown · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: commercial_oss · license: Apache-2.0 · platforms: WEB · deployment: browser, api_only, self_hosted, cloud_managed
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: vakamo.com · github.com. These links do not verify the individual claims.
Lakekeeper is a Databases (SQL, NoSQL, vector, graph) project. Inferred · not functionally tested: It focuses on controlling and auditing access to data across analytics engines, applications, and AI agents. Inferred · not functionally tested: It is built as an open-source project for data platform, security, and compliance teams. Basis unknown · not verified: It follows a commercial open-source model under the Apache-2.0 license. Basis unknown · not verified: Lakekeeper is available on the web and API, and it can be self-hosted.
It is developed by Vakamo, and it first shipped in 2024. The project is developed in the open on GitHub with 1.4k stars and 144 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include access policies, credential vending, and audit trails. Inferred · not functionally tested: Catalogued interfaces include a public API.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Access policies
- Credential vending
- Audit trails
- Apache Iceberg catalog
- AI agent controls
- Air-gapped deployment
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit 26e45dd723fc · since Aug 2026
- Vue
- bdata-v- in the HTML
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed11 Sep · 01:40 UTCThe Ungoverned State of Agent Memory seen via DEV.to articlesSource: DEV.to articles · Open
Frequently asked questions about Lakekeeper
- What does Lakekeeper do?
- Inferred · not functionally tested: Lakekeeper focuses on controlling and auditing access to data across analytics engines, applications, and AI agents. It is catalogued under Databases (SQL, NoSQL, vector, graph) on PulseGate.
- Who should use Lakekeeper?
- Inferred · not functionally tested: Lakekeeper is an open-source project built for data platform, security, and compliance teams.
- Is Lakekeeper free?
- Basis unknown · not verified: The core is open source (Apache-2.0), with commercial offerings on top.
- What platforms does Lakekeeper run on?
- Basis unknown · not verified: Lakekeeper runs on the web and API. It can also be self-hosted.
- Is Lakekeeper still maintained?
- PulseGate's liveness check found it on 11 Sep 2026. Its GitHub repository shows 144 commits in the last 90 days.
- What are alternatives to Lakekeeper?
- Similar projects tracked by PulseGate include LakeOps, MemoryLake, and lakeFS.LakeOpsMemoryLakelakeFS
- Who develops Lakekeeper?
- Lakekeeper is developed by Vakamo.
- When did Lakekeeper launch?
- Lakekeeper first shipped in 2024.
Similar projects
Closest matches by what these projects do