Files
lancedb/docs/web/enterprise/index.mdx
T
Brendan Clement 06aa526ae1 docs: correct data workflows, SQL and operations (#4534)
This PR is part of the documentation revamp. Once the full set of PRs is
merged, we’ll publish the combined site to staging for review before
updating docs.lancedb.com.

The curation, SQL and operations pages contain outdated claims and
examples that do not reliably work as written.

This corrects those pages against the reviewed SDK and local server
evidence, including prepared statements, background jobs, cleanup and
monitoring. Integration guides are grouped with their examples in #4533.

Function and Secret-object documentation stays unpublished until its
release. The two Function pages are listed in `.mintignore` and left out
of the navigation, and the sections about them on other pages are MDX
comments.

Stacked on #4533. Each MDX file has one PR owner. Rebase onto main after
#4533 is squash-merged.

Local assembly, Mint validation and link checks pass, and the assembled
site shows no Function or Secret-object content. A local release
rehearsal that uncomments the drafts and restores the navigation also
passes. Hold publication until this PR and lancedb/sophon#8688 are on
`main`.
2026-10-15 14:57:20 -07:00

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.