Metaxy + LanceDB

Metaxy implements LanceDBMetadataStore. LanceDB keeps one Lance table per feature, writes metadata in append mode, and uses the in-memory Polars versioning engine for provenance calculations. LanceDB handles schema evolution, transactions, and compaction automatically.

It runs embedded (local directory) or against external storage (object stores, HTTP endpoints, LanceDB Cloud), so you can use the same store for local development and remote compute.

Installation

The backend relies on lancedb, which is shipped with Metaxy's lancedb extras.

pip install 'metaxy[lancedb]'

Storage Targets

Point uri at any supported URI (s3://, gs://, az://, db://, ...) and forward credentials with the platform's native mechanism (environment variables, IAM roles, workload identity, etc.). LanceDB supports local filesystem, S3, GCS, Azure, LanceDB Cloud, and remote HTTP/HTTPS endpoints.

Storage Layout

All tables are stored within a single LanceDB database at the configured URI location. Each feature gets its own Lance table.

Reference

• Configuration
• API