Skip to content

Commit d6350d9

Browse files
Clarify OSS vs Enterprise scale in FAQ (#206)
Generated-By: mintlify-agent Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
1 parent cdb7457 commit d6350d9

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

docs/faq/faq-oss.mdx

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,9 @@ The Lance data format that powers our storage system also provides true zero-cop
3434

3535
### How large of a dataset can LanceDB handle?
3636

37-
LanceDB and its underlying data format, Lance, are built to scale to really large amounts of data (hundreds of terabytes). We are currently working with customers who regularly perform operations on 200M+ vectors, and we're fast approaching billion scale and beyond, which are well-handled by our disk-based indexes, without you having to break the bank.
37+
LanceDB and its underlying data format, Lance, are built to scale to really large amounts of data. LanceDB OSS can comfortably handle millions of vectors on a single node, making it a great fit for most applications. Its disk-based indexes keep performance strong without requiring expensive infrastructure.
38+
39+
If you need to scale to hundreds of millions of vectors or work with terabytes of data, we recommend [LanceDB Enterprise](/enterprise). Enterprise customers regularly operate on billions of rows, backed by distributed infrastructure designed for large-scale production workloads.
3840

3941
### Do I need to build a vector index to run vector search?
4042

0 commit comments

Comments
 (0)