Ready to dive into the lake?
lakeFS is currently only
available on desktop.

For an optimal experience, provide your email below and one of our lifeguards will send you a link to start swimming in the lake!

lakeFS Community

lakeFS cloud

Enjoy all the benefits of a Git-like version control interface for your data
lake, in a fully managed service. No deployment, installing, maintaining and
scaling overhead.

cloud-ng
awsplink

Seamless upgrades
and uptime SLA

Enterprise support

SOC2 compliance

Frequently Asked Questions

Where is my data stored?

The data you wish to version control will stay in place on your object storage. Onboarding data to lakeFS is done by creating the lakeFS metadata for your existing data while the data stays in place. While writing new data using lakeFS, the bucket you define for lakeFS on your object storage will be used to store that data.

What data is stored in lakeFS Cloud?

lakeFS cloud holds lakeFS metadata that is used to ensure the performance of data version control operations such as diff and merge. lakeFS cloud Does Not store any of your data. If used correctly, it doesn’t even access it.

What permissions do you need for lakeFS Cloud, and why?

The lakeFS user running the import command needs to have the following permissions in lakeFS: fs:WriteObject, fs:CreateMetaRange, fs:CreateCommit, fs:ImportFromStorage and fs:ImportCancel (all are available by default to the Supers or SuperUsers group). In addition, provider-specific permissions may be required for Amazon S2 and Azure Storage.

What integrations are available with SSO?

lakeFS Cloud uses Auth0 for authentication; therefore, it supports the same identity providers as Auth0: Active Directory/LDAP, ADFS, Azure Active Directory Native, Google Workspace, OpenID Connect, Okta, PingFederate, SAML, and Azure Active Directory. In lakeFS Enterprise, authentication is handled via a secondary service running side-by-side with lakeFS, Fluffy.

What are the enterprise/cloud RBAC capabilities?

The lakeFS RBAC model manages access to resources similarly to the AWS IAM, and includes concepts such as Users, Actions, Resources, Policies, Groups. Controlling access is done by attaching Policies, either directly to Users or Groups to which they belong

 

Every action in the system – for example, an API request – requires a set of other actions to be allowed for one or more resources. When a user makes a request to perform that action, the process follows with authentication, action permission resolution, effective policy resolution, and policy/permission evaluation to determine whether or not the request is allowed to continue.

Git for Data – lakeFS

  • Get Started
    Get Started