Cloudflare AI Search vs LanceDB

Cloudflare AI Search

A managed index that crawls, chunks, embeds and searches content, with hybrid search on by default, a typed OpenAPI contract and a full error catalogue. Generally available since 1 October 2026, with billing from 1 November. Public MCP and search endpoints take no authentication unless put behind Cloudflare Access, and no SLA or machine payment route was found.

LanceDB

Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.

Cloudflare AI Search

1. Use /ai-search/namespaces/default/instances/{id}/search. The un-namespaced and /autorag/rags/ paths are deprecated
2. Set ai_search_options.retrieval.max_num_results (1 to 50, default 10) and match_threshold (default 0.4) to bound the context you read
3. On 429 code 7069 the monthly query quota is spent. Wait or upgrade rather than retry
4. Expect up to six hours before website or R2 changes are searchable. Trigger a sync job, at most once every 30 seconds, after you write
5. Filters match only the first 64 bytes of a string. Use a $gte/$lt range on folder to match a folder and its subfolders

LanceDB

1. Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
2. Build an FTS index before calling query_type="hybrid", or hybrid search has no keyword side
3. Call optimize() after many small writes, since each write adds a new file version
4. Use select() to drop the vector column from results unless the task needs it
5. On object storage, set a read consistency interval if several processes write the same table