lancedb

lance: Store and Query Multimodal Lakehouse Data

Lance is a Rust-based lakehouse format and SDK for AI and machine-learning data. It combines columnar storage with random access, vector and full-text search, and dataset versioning for teams working with multimodal data.

View on GitHub Compare
Stars
7.1k
Forks
876
Stars, last 30 days
+183

Our take

Health score

73/100

How it is scored
Activity
90
Community
93
Issues
69
Pull requests
40

+183 stars in the last 30 days

  • Releases more often than 93% of the projects we track
  • More contributors than 78% of the projects we track
  • Slower to merge pull requests than 92% of the projects we track

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

7,354

Forks

951

Change since Nov 17, 2026: +10 stars·+4 forks

Overview

Lance is a file and table format, with a catalog specification, for storing and working with AI and analytics datasets on object storage. It targets a gap in conventional analytics formats: workloads that need efficient random access, multimodal records, and search capabilities alongside columnar scans.

The project includes a Rust core and SDK bindings, including Python. It may suit teams building data pipelines, feature stores, or search systems that want these capabilities within a lakehouse dataset rather than assembling separate storage and indexing systems.

Key Features

  • Stores tabular data alongside multimodal content such as images, video, audio, text, and embeddings.
  • Supports vector similarity search, BM25 full-text search, and SQL analytics on datasets.
  • Provides random-access reads intended for sampling, exploration, and training workloads.
  • Supports adding columns with backfilled values without rewriting the full table.
  • Provides dataset versioning with ACID transactions, time travel, tags, and branches.
  • Integrates with tools including Arrow, Pandas, Polars, DuckDB, Spark, and Ray.
  • Offers Rust and Python implementations, with Java bindings also listed in the repository.

Use Cases

  • ML platform teams can use Lance datasets as feature stores that combine vector retrieval with structured filters and analytics.
  • Data engineers preparing large training datasets can use random access for sampling and can store embeddings or media alongside tabular fields.
  • Search developers can build retrieval workflows over vector and text indexes without separating those indexes from the dataset.
  • Analytics teams working with images, audio, or video can keep metadata and multimodal data in a shared dataset for exploration and querying.

Getting Started

Install the Python package:

pip install pylance

See the README for conversion, reading, and vector search examples, and the documentation for format and SDK details.

Considerations

  • The project is in active development. SDK and API compatibility is separate from file-format compatibility, so check the migration guidance when upgrading.
  • For production datasets, select a stable data_storage_version. The README says the next alias is unstable and intended only for experimentation.
  • Older Lance releases may not read storage versions introduced by newer releases. Mixed-version deployments should pin the storage version.
  • Integrations and SDKs span several ecosystems, so confirm that the required language binding and integrations meet your deployment needs.

Found this useful?

Share it with someone who would like lance.

Comparisons