mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-20 10:42:26 +00:00
The existing docs have 254 findings from our shared Vale rules. Contributors would otherwise inherit these when editing the same lines. Clean up the prose across 80 pages: correct product names and a repeated word, simplify a few phrases, and replace dashes with punctuation that fits each sentence. The pinned Vale scan now reports zero findings, with no suppressions.
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
---
|
|
title: "LanceDB Enterprise"
|
|
sidebarTitle: "Overview"
|
|
description: "What a deployment adds over embedded LanceDB."
|
|
icon: building
|
|
keywords: ["enterprise", "deployment", "cluster"]
|
|
---
|
|
|
|
<Badge color="red">Enterprise</Badge>
|
|
|
|
This page describes a LanceDB Enterprise capability. The embedded form
|
|
of LanceDB has no server to provide it. See
|
|
[Architecture](/architecture) for what differs between the two.
|
|
|
|
LanceDB Enterprise runs the lakehouse as a service: a control plane for
|
|
configuration, identity and policy; a data plane serving reads and writes; and
|
|
indexers building indexes and compacting outside the request path.
|
|
|
|
What it adds over the embedded form:
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| [SQL](/sql) | an Arrow Flight SQL endpoint |
|
|
| [Jobs](/basics/jobs) | server-side work with ids, status and events |
|
|
| [Authorization](/governance/authorization) | per-object grants |
|
|
| Scale | a cluster rather than your process |
|
|
|
|
{/*
|
|
Draft for the Functions release. Add this row to the table above, after SQL:
|
|
| [Functions](/management/function) | Python running on workers |
|
|
*/}
|
|
|
|
See [Architecture](/architecture) for the two shapes side by side.
|