lakeFS
PulseGate's liveness check found it on 28 Sep 2026; it is registered on GitHub and has been in the index since 28 Sep 2026. How this is checked
lakeFS is a data version control and governance platform that provides Git-like branching, commits, and rollback for data stored in object storage. It helps AI and data engineering teams manage provenance, isolated access, reproducible experiments, and compliance workflows.
Inferred · not functionally tested
Overview
6 featuresPurpose: Managing, versioning, governing, and reproducing data workflows for AI and data engineering.
Inferred · not functionally tested
Audience: AI engineers, data engineers, and ML teams
Inferred · not functionally tested
Functions: data_extraction, workflow_automation, collaboration
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: enterprise_only · license: Proprietary · platforms: WEB · deployment: browser, cloud_managed, self_hosted, api_only, cli
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: lakefs.io · github.com. These links do not verify the individual claims.
lakeFS is a Databases (SQL, NoSQL, vector, graph) project. Inferred · not functionally tested: Managing, versioning, governing, and reproducing data workflows for AI and data engineering. Inferred · not functionally tested: It is built as a B2B product for AI engineers, data engineers, and ML teams. Basis unknown · not verified: Pricing is enterprise-only. Basis unknown · not verified: lakeFS is available on the web, API, and the command line, and it can be self-hosted.
It is developed by lakeFS, and it first shipped in 2019. The project is developed in the open on GitHub with 5.5k stars and 27 commits in the last 90 days. Inferred · not functionally tested: Among its 6 catalogued features are data version control, git-like branching, and data provenance. 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
- Data version control
- Git-like branching
- Data provenance
- Data governance
- Access controls
- Reproducible experiments
Topics: Inferred · not functionally tested
Built with & integrations
- Claude Code
- commit bd312de8bec5 · since Jun 2026
- WordPress
- /wp-content/ in the HTML · /wp-json/ in the HTML · /wp-includes/ in the HTML
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed28 Sep · 08:06 UTCGive your AI agent a versioned filesystem seen via Hacker News firehose (Algolia)Source: Hacker News firehose (Algolia) · Open
Frequently asked questions about lakeFS
- What is lakeFS?
- Inferred · not functionally tested: Managing, versioning, governing, and reproducing data workflows for AI and data engineering. It is catalogued under Databases (SQL, NoSQL, vector, graph) on PulseGate.
- Who is lakeFS for?
- Inferred · not functionally tested: lakeFS is a B2B product built for AI engineers, data engineers, and ML teams.
- Is lakeFS free?
- Basis unknown · not verified: No — lakeFS is sold on an enterprise-only basis.
- What platforms does lakeFS run on?
- Basis unknown · not verified: lakeFS runs on the web, API, and the command line. It can also be self-hosted.
- Is lakeFS still active?
- PulseGate's liveness check found it on 28 Sep 2026. Its GitHub repository shows 27 commits in the last 90 days.
- Who develops lakeFS?
- lakeFS is developed by lakeFS.
- How long has lakeFS been around?
- lakeFS first shipped in 2019.
- Is lakeFS open source?
- Basis unknown · not verified: lakeFS has a public GitHub repository.
Similar projects
Closest matches by what these projects do