---
title: Web and Cloudflare
order: 20
date: 2026-03-25
summary: Load canonical bundles in browsers, workers, and Cloudflare Workers.
---

# Web and Cloudflare

`indexbind` has two web-facing entrypoints:

- `indexbind/web`
- `indexbind/cloudflare`

They both query canonical bundles, but Cloudflare Workers need a dedicated entry so wasm can load through a static Worker module import.

## Browser or Standard Worker

```ts
import { openWebIndex } from 'indexbind/web';

const index = await openWebIndex('/search/index.bundle');
const hits = await index.search('cloudflare wasm');
```

If your site always uses lexical-only retrieval, open the bundle with a lexical profile so vectors and model files are not loaded for that runtime instance:

```ts
const index = await openWebIndex('/search/index.bundle', {
  modeProfile: 'lexical',
});
const hits = await index.search('cloudflare wasm');
```

## Cloudflare Worker

```ts
import { openWebIndex } from 'indexbind/cloudflare';

export default {
  async fetch(request: Request): Promise<Response> {
    const index = await openWebIndex('https://assets.example.com/index.bundle');
    const hits = await index.search(new URL(request.url).searchParams.get('q') ?? '');
    return Response.json(hits);
  },
};
```

If your host virtualizes bundle files instead of exposing public bundle URLs, pass a custom `fetch` implementation:

```ts
const index = await openWebIndex(new URL('https://mdorigin-search.invalid/index.bundle/'), {
  fetch: (input, init) => env.ASSETS.fetch(new Request(input, init)),
});
```

If your host application serves bundle files through Workers Assets and a virtual base URL, see the manual testcase in:

- `fixtures/manual/cloudflare-worker-issue-18`

It reproduces the same shape as `mdorigin`: a fake bundle origin plus a temporary `fetch` redirect into `ASSETS.fetch(...)`.

## Embedding Backends

Canonical bundles can currently be built with:

- `hashing`
- `model2vec`

Use `model2vec` as the default recommended backend when you want the higher-quality retrieval path. Use `hashing` when you want a lighter compatibility-oriented backend or a smaller build dependency surface.

For `model2vec`, the build step copies these files into the bundle:

- `model/tokenizer.json`
- `model/config.json`
- `model/model.safetensors`

That lets the wasm runtime embed queries without host filesystem access.

## Package Boundary

The npm package contains runtime code and wasm files.

The bundle artifact contains your actual index data, vectors, postings, and optional `model2vec` model files.