Lamin Labs

license

Apache-2.0(OSI)

source

public

core features withheld

no

Apache-2.0 license body confirmed. The repository is public and unarchived and builds the whole library, and the README describes no paid tier, enterprise edition or license-gated build beside it - LaminHub is a separately sold hosted service rather than a piece withheld from the published library.

• https://api.github.com/repos/laminlabs/lamindb recorded 2026-09-02

  Repo metadata - license spdx_id Apache-2.0, private false, archived false, default branch main - for laminlabs/lamindb.

• https://github.com/laminlabs/lamindb/blob/main/LICENSE recorded 2026-10-07

  LICENSE file is the verbatim Apache-2.0 text.

• https://github.com/laminlabs/lamindb/blob/main/README.md recorded 2026-10-07

  README describes an open-source data management library with no paid tier, enterprise edition or license-key-gated build beside the Apache-2.0 library, only the separately sold LaminHub service.

LaminDB's adoption reading comes from PyPI downloads of the `lamindb` package, since LaminDB is a Python library with no separate server, so the package is the product itself rather than a client to one. This is a direct signal of use, though it counts only PyPI installs and not use through other channels.

• https://api.github.com/repos/laminlabs/lamindb recorded 2026-09-02

  Repo metadata - stargazers_count = 365 - for laminlabs/lamindb.

• https://pypistats.org/api/packages/lamindb/recent recorded 2026-09-02

  last_month downloads = 75,817 for lamindb.

LaminDB is a metadata and lineage registry, backed by SQLite or Postgres, that tracks, versions and federates files, tables and arrays across pluggable storage locations rather than storing the data itself. That puts it alongside DVC: both provide lineage, versioning and governance over storage they do not themselves provide, rather than a distributed storage system in their own right.

• https://github.com/laminlabs/lamindb/blob/main/README.md recorded 2026-10-07

  README: LaminDB "generalizes core lakehouse guarantees — ACID transactions, time travel, and schema evolution — to multimodal data", with metadata in SQLite/Postgres and data in parquet, zarr and other formats across local, S3 and GCP storage, and no storage engine of its own.