From 83593fee97c678935841f58ca44467b50d6f6ef6 Mon Sep 17 00:00:00 2001 From: Brendan Clement Date: Fri, 9 Oct 2026 09:13:45 -0700 Subject: [PATCH] docs: name the storage page for embedded storage configuration "Storage | Yes / No" and an OSS tag on a page called Storage read as if Enterprise had no storage. The difference the code shows is narrower: the embedded library configures its storage backend from the connection, while a deployment sets up its own and a db:// connection passes none of those options except an Azure storage account name. The page is now Embedded storage configuration, says so first, and points deployments to their own setup. The declaration is unchanged. --- docs/web/deployment/storage.mdx | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/web/deployment/storage.mdx b/docs/web/deployment/storage.mdx index 55426b23a..3455cf614 100644 --- a/docs/web/deployment/storage.mdx +++ b/docs/web/deployment/storage.mdx @@ -1,7 +1,7 @@ --- -title: "Storage" -sidebarTitle: "Storage" -description: "Choosing and configuring where LanceDB stores its data -- how you deploy an embedded database." +title: "Embedded storage configuration" +sidebarTitle: "Embedded Storage" +description: "Choosing and configuring where embedded LanceDB stores its data -- how you deploy an embedded database." icon: database keywords: ["storage", "s3", "gcs", "azure", "object store", "configuration", "deploy"] availability: @@ -13,6 +13,12 @@ availability: the deployment's own configuration instead. --- +This page is about the embedded library, where your connection chooses and +configures the storage backend. A LanceDB Enterprise deployment sets up its own +storage when it is deployed, so a `db://` connection passes none of these +options except an Azure storage account name -- see +[Deployment](/enterprise/deployment) for how a deployment is set up. + LanceDB's storage layer is built on modular, disk-first components. That design makes it flexible enough to run across local NVMe, EBS, EFS, and any object store that exposes an S3-compatible API. It also supports region-specific backends such as [Tencent COS](/storage/configuration#tencent-cos) and cache-acceleration layers such as [GooseFS](/storage/configuration#goosefs). Choosing a backend is a balance between latency, scalability, cost, and operational complexity. Use this guide to pick the right fit for your workload.