l

lakeFS

by Treeverse

Data & AnalyticsInfrastructure & CloudGovernance & Security

Git-style branching, commits and rollback for data lakes and AI training data.

Free · Contact for pricing·Added Jul 12, 2026·Updated Sep 22, 2026
Share:
THE DAILY BRIEF
lakeFS

by Treeverse

Data & AnalyticsInfrastructure & CloudGovernance & Security

Git-style branching, commits and rollback for data lakes and AI training data.

Free · Contact for pricing

lakeFS is an open-source, Git-style version control layer for data lakes that lets data engineering and ML teams branch, commit, merge and roll back petabyte-scale object storage without copying data. It suits organisations that need reproducible training datasets, isolated testing on production data and an audit trail for AI data governance. Enterprise and managed Cloud editions add RBAC, SSO and hosted operations.

At a Glance

Category
Data & Analytics
Pricing
Free, Contact for pricing
Target Market
CTOs, CIOs, Data Engineers, ML Engineers, Data Scientists
Deployment
Open-source, Self-hosted, Hybrid
Founded
2020
Headquarters
New York, United States
Customers
Thousands of organizations use lakeFS (company claim, July 2025)

Key Features

  • ✓Zero-copy branching
  • ✓Atomic commits, merges and reverts
  • ✓Hooks for write-audit-publish
  • ✓S3-compatible gateway
  • ✓Format-agnostic versioning
  • ✓Apache Iceberg REST catalog
  • ✓lakeFS Mount
  • ✓Enterprise access control and mirroring

Capabilities

✗text generation
✗image generation
✗video generation
✗code generation
✗workflow automation
✓api access
✗audio generation
✗fine tuning
✗agent orchestration

Use Cases

  • •Reproducible ML training
  • •Testing pipelines on production data
  • •Data incident rollback
  • •Sandboxes for AI agents
  • •Write-audit-publish quality gates

Ideal For

Best For

  • ✓Data platform teams running Spark, Databricks, Presto or Athena over S3, Azure Blob or GCS object storage
  • ✓ML teams that must reproduce the exact training data behind a model for audit or regulatory review
  • ✓Organisations testing ETL and dbt changes against full production data without duplicating storage
  • ✓Teams versioning unstructured multimodal data such as images, video and sensor data for AI training
  • ✓Regulated or defence environments that need self-hosted or air-gapped deployment (Enterprise edition)

Not Ideal For

  • ✗Teams that need multi-user permissions but will not pay: the Community edition runs with a single administrator user, and RBAC and SSO are Enterprise-only.
  • ✗Individual data scientists versioning small datasets next to a Git repo, for whom DVC (now also owned by lakeFS) or Git LFS is a lighter fit.
  • ✗Teams whose data lives entirely in warehouse-managed storage such as native Snowflake or BigQuery tables, where lakeFS's object-storage versioning does not apply.

Market Analysis

Open-source coreEnterprise-gradeAI data infrastructure

Pros

  • ✓Apache 2.0 open-source core in Go with an active release cadence (five releases between 9 July and 5 August 2026)
  • ✓Zero-copy branching enables testing and experimentation on full production data without storage duplication
  • ✓S3-compatible API and broad integrations (Spark, Databricks, Snowflake, Airflow, dbt, MLflow, Hugging Face) reduce adoption friction
  • ✓Enterprise edition runs managed, on-premises, in a customer cloud or air-gapped
  • ✓$43M raised and named users including NASA, Volvo, Lockheed Martin, Arm and the U.S. Department of Energy

Cons

  • ✗ACLs were removed from the open-source edition in 2024 and Community now runs with a single administrator user; Hacker News commenters called it a push toward the paid tier, since RBAC and SSO are Enterprise-only
  • ✗No published pricing for lakeFS Cloud or Enterprise, so every paid deployment requires a sales conversation
  • ✗The GitHub repository carried 359 open issues in September 2026, and v1.86.0 (August 2026) patched a flaw that let users without fs:ListRepositories list repositories via the S3 gateway
  • ✗Self-hosted deployments put a metadata service and S3 gateway in the data path and require garbage-collection jobs to reclaim storage from deleted versions

Pricing

lakeFS Community (open source)

$0

  • ✓Apache 2.0 licence, self-hosted
  • ✓Git-like branches, commits, merges, tags and hooks
  • ✓S3-compatible gateway and Python SDK
  • ✓Single administrator user (no RBAC or SSO)

lakeFS Enterprise

Contact for pricing

  • ✓Managed service on lakeFS Cloud or self-hosted
  • ✓On-premises, own-cloud or air-gapped deployment
  • ✓RBAC, SSO and SCIM provisioning
  • ✓Transactional mirroring

The Community edition is free under the Apache 2.0 licence. lakeFS publishes no list prices: its pricing page describes only lakeFS Enterprise, delivered as a managed service on lakeFS Cloud or self-hosted on-premises, in a customer cloud or air-gapped, and routes buyers to sales. The metering basis for paid plans is not disclosed.

Security & Compliance

✓soc2
✗gdpr
✗hipaa
✗iso27001
✓sso
✗data residency

THE DAILY BRIEF

Enterprise AI insights for technology and business leaders, weekly.

beri.net

Subscribe at beri.net/subscribe for weekly AI insights delivered to your inbox.

LinkedIn: linkedin.com/in/rberi  |  X: x.com/rajeshberi

© 2026 Rajesh Beri. All rights reserved.

lakeFS is an open-source, Git-style version control layer for data lakes that lets data engineering and ML teams branch, commit, merge and roll back petabyte-scale object storage without copying data. It suits organisations that need reproducible training datasets, isolated testing on production data and an audit trail for AI data governance. Enterprise and managed Cloud editions add RBAC, SSO and hosted operations.

lakeFS is an open-source data version control system from Treeverse that turns object storage such as Amazon S3, Azure Blob Storage, Google Cloud Storage and S3-compatible stores like MinIO into a Git-like repository, so teams can branch, commit, merge, tag and revert data the way developers manage code. Branches are zero-copy: lakeFS creates them without duplicating the underlying objects, which lets engineers test pipelines, run ML experiments or let AI agents work against a full production snapshot in isolation, then merge atomically or roll back a bad load. Applications reach it through an S3-compatible gateway, generated API clients and a high-level Python SDK, and hooks fired on commits, merges and branch creation enforce write-audit-publish quality gates. The core is written in Go under the Apache 2.0 licence; the GitHub repository showed about 5.5k stars, 479 forks and 359 open issues in September 2026, with five releases between 9 July and 5 August 2026 (latest v1.86.0). Treeverse, founded in 2020 by Einat Orr and Oz Katz and headquartered in New York, first released lakeFS in August 2020, launched the managed lakeFS Cloud in June 2022 and shipped 1.0 in October 2023. It now markets the product as a control plane for AI-ready data, adding lakeFS Mount, an Apache Iceberg REST catalog and transactional mirroring. The free Community edition runs with a single administrator user; RBAC, SSO and SCIM belong to lakeFS Enterprise, offered as a managed service on lakeFS Cloud or self-hosted on-premises, in a customer's own cloud or air-gapped. Treeverse raised a $20M round led by Maor Investments in July 2025, taking total funding to $43M, and acquired the DVC project in November 2025. Named users include Arm, Bosch, Lockheed Martin, NASA, Volvo and the U.S. Department of Energy.

Ideal Buyer

Heads of data platform or MLOps running a lakehouse on S3, Azure Blob or GCS who need reproducible, auditable datasets for AI without copying data.

Key Benefit

Safe, zero-copy experimentation and instant rollback on production data, with every model tied to an exact, reproducible dataset commit.

At a Glance

Category
Data & Analytics
Pricing
Free, Contact for pricing
Target Market
CTOs, CIOs, Data Engineers, ML Engineers, Data Scientists
Deployment
Open-source, Self-hosted, Hybrid
Founded
2020
Headquarters
New York, United States
Customers
Thousands of organizations use lakeFS (company claim, July 2025)

Key Features

  • ✓
    Zero-copy branching

    Creates isolated branches of an entire repository without duplicating the underlying objects, so teams can test changes on full production data cheaply.

  • ✓
    Atomic commits, merges and reverts

    Commits are immutable snapshots and merges update a branch atomically, which makes instant rollback after a bad pipeline run or data incident possible.

  • ✓
    Hooks for write-audit-publish

    Hooks triggered on commits, merges and branch creation run validation checks before data reaches consumers, turning quality rules into enforced gates.

  • ✓
    S3-compatible gateway

    Exposes repositories through an S3-compatible API, so Spark, Athena, Presto, DuckDB and boto3 clients work with minimal code changes.

  • ✓
    Format-agnostic versioning

    Versions Delta Lake, Iceberg, Hudi and Parquet tables alongside unstructured images, video and sensor data under one versioning model for multimodal AI datasets.

  • ✓
    Apache Iceberg REST catalog

    Adds an Iceberg REST catalog, announced in mid-2025, so Iceberg-compatible engines can work with version-controlled structured tables through the standard catalog protocol.

  • ✓
    lakeFS Mount

    Mounts a lakeFS repository locally so ML training code and notebooks can read versioned data as ordinary files without custom loaders.

  • ✓
    Enterprise access control and mirroring

    lakeFS Enterprise adds role-based access control, single sign-on, SCIM provisioning and transactional mirroring, which the single-admin Community edition lacks.

Capabilities

✗text generation
✗image generation
✗video generation
✗code generation
✗workflow automation
✓api access
✗audio generation
✗fine tuning
✗agent orchestration

Use Cases

  • •
    Reproducible ML training

    Tag the exact commit a model was trained on so auditors or engineers can reproduce the training dataset months later for compliance reviews.

  • •
    Testing pipelines on production data

    Run a changed Spark or dbt pipeline on a zero-copy branch of production data, validate the output, then merge atomically instead of testing on stale samples.

  • •
    Data incident rollback

    When a bad load corrupts a table or dataset, revert the branch to the last good commit instead of restoring from backups, cutting downtime for consumers.

  • •
    Sandboxes for AI agents

    Give AI agents an isolated branch of real data to read and write, then review and merge their changes only after automated checks pass.

  • •
    Write-audit-publish quality gates

    Use pre-merge hooks with tools such as Great Expectations to block data that fails quality checks from reaching the production branch.

Ideal For

Best For

  • ✓Data platform teams running Spark, Databricks, Presto or Athena over S3, Azure Blob or GCS object storage
  • ✓ML teams that must reproduce the exact training data behind a model for audit or regulatory review
  • ✓Organisations testing ETL and dbt changes against full production data without duplicating storage
  • ✓Teams versioning unstructured multimodal data such as images, video and sensor data for AI training
  • ✓Regulated or defence environments that need self-hosted or air-gapped deployment (Enterprise edition)

Not Ideal For

  • ✗Teams that need multi-user permissions but will not pay: the Community edition runs with a single administrator user, and RBAC and SSO are Enterprise-only.
  • ✗Individual data scientists versioning small datasets next to a Git repo, for whom DVC (now also owned by lakeFS) or Git LFS is a lighter fit.
  • ✗Teams whose data lives entirely in warehouse-managed storage such as native Snowflake or BigQuery tables, where lakeFS's object-storage versioning does not apply.

Integrations

✓SDK Available
SDK:Python

Deployment

✓On-Premise

Market & Ratings

Estimated Customers

Thousands of organizations use lakeFS (company claim, July 2025)

Market Analysis

Open-source coreEnterprise-gradeAI data infrastructure

Pros

  • ✓Apache 2.0 open-source core in Go with an active release cadence (five releases between 9 July and 5 August 2026)
  • ✓Zero-copy branching enables testing and experimentation on full production data without storage duplication
  • ✓S3-compatible API and broad integrations (Spark, Databricks, Snowflake, Airflow, dbt, MLflow, Hugging Face) reduce adoption friction
  • ✓Enterprise edition runs managed, on-premises, in a customer cloud or air-gapped
  • ✓$43M raised and named users including NASA, Volvo, Lockheed Martin, Arm and the U.S. Department of Energy

Cons

  • ✗ACLs were removed from the open-source edition in 2024 and Community now runs with a single administrator user; Hacker News commenters called it a push toward the paid tier, since RBAC and SSO are Enterprise-only
  • ✗No published pricing for lakeFS Cloud or Enterprise, so every paid deployment requires a sales conversation
  • ✗The GitHub repository carried 359 open issues in September 2026, and v1.86.0 (August 2026) patched a flaw that let users without fs:ListRepositories list repositories via the S3 gateway
  • ✗Self-hosted deployments put a metadata service and S3 gateway in the data path and require garbage-collection jobs to reclaim storage from deleted versions

Pricing

lakeFS Community (open source)

$0

  • ✓Apache 2.0 licence, self-hosted
  • ✓Git-like branches, commits, merges, tags and hooks
  • ✓S3-compatible gateway and Python SDK
  • ✓Single administrator user (no RBAC or SSO)

lakeFS Enterprise

Contact for pricing

  • ✓Managed service on lakeFS Cloud or self-hosted
  • ✓On-premises, own-cloud or air-gapped deployment
  • ✓RBAC, SSO and SCIM provisioning
  • ✓Transactional mirroring

The Community edition is free under the Apache 2.0 licence. lakeFS publishes no list prices: its pricing page describes only lakeFS Enterprise, delivered as a managed service on lakeFS Cloud or self-hosted on-premises, in a customer cloud or air-gapped, and routes buyers to sales. The metering basis for paid plans is not disclosed.

Security & Compliance

✓soc2
✗gdpr
✗hipaa
✗iso27001
✓sso
✗data residency

Connect

Sources

This page was written from 12 sources, 8 on domains other than lakefs.io.

  1. 1.lakefs.io — lakefs.iovendor
  2. 2.lakefs.io — pricingvendor
  3. 3.lakefs.io — securityvendor
  4. 4.docs.lakefs.io — access control lists
  5. 5.docs.lakefs.io — python
  6. 6.lakefs.io — celebration shared vision lakefs dvcvendor
  7. 7.github.com — lakeFS
  8. 8.github.com — releases
  9. 9.hn.algolia.com — 41061786
  10. 10.prnewswire.com — git for data pioneer lakefs secures 20m in growth capital fi
  11. 11.dbta.com — lakeFS Secures 20M in Growth Capital Transforms Critical Gap
  12. 12.en.wikipedia.org — LakeFS
Newsletter

Stay Ahead of the Curve

Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.

Subscribe