Files
lancedb/docs/web/enterprise/security.mdx
T
d67ec47921 docs: make the landing page concise (#4898)
Shortens the docs landing page and organizes its overview around
database features, with the multimodal data model, ML workflow, SDKs,
and PyTorch loader explained in prose. Keeps versioning visible,
branching in draft, and the existing `{#architecture}` anchor.

Validation: added documentation links and anchors verified; `git diff
--check` passes. `mint validate` reports the same four pre-existing
missing snippet-export warnings in the reranking and vector-search
pages, also reproduced on the unchanged revision.

Closes
https://linear.app/lancedb/issue/DOC-80/strengthen-what-is-lancedb

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Brendan Clement <brendan.clement@lancedb.com>
2026-11-13 20:23:41 -08:00

22 lines
884 B
Plaintext

---
title: "Compliance"
sidebarTitle: "Compliance"
description: "Certifications, data handling, and the controls a deployment provides."
icon: certificate
keywords: ["compliance", "security", "soc2", "encryption", "audit"]
---
<Badge color="red">Enterprise</Badge>
This page describes a LanceDB Enterprise capability. The embedded form
of LanceDB has no server to provide it. See
[Embedded vs Enterprise](/basics/embedded-vs-enterprise) for what differs between the two.
Compliance posture (certifications, data residency, encryption at rest and in
transit, audit logging) is a property of a deployment, so it is documented
with LanceDB Enterprise. See [Audit Log](/governance/audit-log) for the
audit log's schema and how to query it.
For LanceDB Embedded, these are properties of the object store you point it at
and the process you run it in; LanceDB adds no layer of its own.