lakeFS Editions¶
lakeFS comes in two editions that share the same core versioning engine and object model. lakeFS Enterprise is the commercially supported edition, backed by an SLA, that adds security, governance, and scalability on top of the shared foundation. You can run it hosted, a fully managed service run by Treeverse and known as lakeFS Cloud, or self-managed, which you install and operate on your own infrastructure. lakeFS Community is the open-source distribution, free to run anywhere.
This page compares the editions and points you to the right place to get started with each.
Choosing an edition¶
lakeFS Enterprise brings production-grade security, governance, and support, whether you run it hosted as a fully managed service or self-managed in your own environment. lakeFS Community gives you the full versioning workflow to operate yourself. Pick the card that fits you.
-
lakeFS Enterprise, hosted
The full Enterprise feature set as a fully managed service, lakeFS Cloud. Treeverse runs a single-tenant, highly available, auto-scaling instance for you, with managed upgrades, managed garbage collection, SOC2 Type II compliance, and an uptime SLA.
-
lakeFS Enterprise, self-managed
The same Enterprise features, including RBAC, SSO, SCIM, auditing, lakeFS Mount, and the Iceberg REST Catalog, running on your own S3-compatible infrastructure with full control over deployment and data locality.
-
lakeFS Community
The open-source distribution, free to run anywhere. Format-agnostic, cloud-agnostic data version control with zero-copy branching, atomic merges, configurable garbage collection, and hooks for data CI/CD. You install and operate it yourself.
Request a free trial at lakefs.io/try to get full access to all Enterprise features, and contact us if you need help choosing.
Release notes
For the latest updates to lakeFS Enterprise, see the release notes.
Feature comparison¶
The table below compares Enterprise and Community. Capabilities that are only available in the hosted deployment of Enterprise are marked hosted only.
| Feature | Enterprise | Community |
|---|---|---|
| Format-agnostic data version control | ✅ | ✅ |
| Cloud-agnostic | ✅ | ✅ |
| Zero-copy branching for isolated environments | ✅ | ✅ |
| Atomic data promotion through merges | ✅ | ✅ |
| Data stays in place, in your object store | ✅ | ✅ |
| Configurable garbage collection | ✅ | ✅ |
| Data CI/CD using lakeFS hooks | ✅ | ✅ |
| Integrates with your data stack | ✅ | ✅ |
| Role-Based Access Control (RBAC) | ✅ | |
| Single Sign-On (SSO) | ✅ | |
| SCIM provisioning | ✅ | |
| AWS IAM role authentication | ✅ (AWS) | |
| lakeFS Mount | ✅ | |
| Iceberg REST Catalog | ✅ | |
| Metadata Search | ✅ | |
| Auditing | ✅ | |
| Transactional mirroring (cross-region) | ✅ | |
| Multiple storage backends | ✅ | |
| Async commit and merge | ✅ | |
| Support SLA | ✅ | |
| Managed service (automatic upgrades and scaling) | ✅ (hosted only) | |
| Managed garbage collection | ✅ (hosted only) | |
| Private Link | ✅ (hosted only) | |
| SOC2 Type II compliance | ✅ (hosted only) |
Async Commit and Merge¶
lakeFS Enterprise provides asynchronous commit and merge operations for improved scalability when working with large repositories.
Atomicity guarantees are unchanged. Async operations are still fully atomic, and the only difference is that the API returns immediately while the operation executes in the background.
Operations return immediately with a task ID, and progress can be monitored by polling the task status. The UI and lakectl use async operations by default and handle the polling automatically, so the experience stays seamless. This keeps the UI and CLI responsive during long-running operations, lets you handle large commits and merges without timeout issues, and lets you track operation progress in real time. See how merges work for the merge-side details.