Cloudflare

Cloudflare edge SSR is the default deployment path for svedocs. Static output is also first-class. SPA output is supported for hosts that need a client-side fallback while still serving prerendered known pages.

Build preset#

TypeScriptsvelte.config.js
1import adapterCloudflare from '@sveltejs/adapter-cloudflare';
2import adapterStatic from '@sveltejs/adapter-static';
3import { createCloudflarePreset } from 'svedocs/cloudflare';
4
5const preset = createCloudflarePreset(process.env.SVEDOCS_BUILD_MODE ?? 'edge');
6
7export default {
8  kit: {
9    adapter: preset.adapter === '@sveltejs/adapter-cloudflare'
10      ? adapterCloudflare({ platformProxy: { remoteBindings: false } })
11      : adapterStatic({ fallback: preset.mode === 'spa' ? '200.html' : undefined })
12  }
13};

Wrangler#

svedocs deploy cloudflare --write creates a baseline wrangler.toml from your resolved config.

TOMLwrangler.toml
1name = "my-docs"
2compatibility_date = "2026-05-18"
3pages_build_output_dir = ".svelte-kit/cloudflare"
4
5[[ai_search]]
6binding = "SVEDOCS_AI_SEARCH"
7instance_name = "svedocs"

For AI Search namespaces, configure cloudflare.aiSearch.namespace; svedocs will emit [[ai_search_namespaces]] instead of [[ai_search]].

platformProxy.remoteBindings is disabled in the local adapter config so edge builds and prerendering do not require a Cloudflare account. cloudflare.aiSearch.remote also defaults to false; set both intentionally only when you want local development to talk to remote Cloudflare resources.

Runtime types#

TypeScriptsvedocs.config.ts
1export default defineConfig({
2  search: { provider: 'cloudflare-ai-search' },
3  ai: { provider: 'cloudflare-ai-search' },
4  cloudflare: {
5    aiSearch: {
6      binding: 'SVEDOCS_AI_SEARCH',
7      instanceName: 'svedocs'
8    }
9  }
10});

The generated platform declaration types the SVEDOCS_AI_SEARCH binding. Workers AI can be enabled with ai.provider = 'cloudflare-workers-ai', which emits the AI binding.

AI Search is opt-in. A default project keeps MiniSearch local search, and only emits AI Search bindings when search.provider or ai.provider is set to cloudflare-ai-search.

Local development#

Cloudflare-backed routes should always keep local fallback behavior. The template search route uses createConfiguredSearchResponse, so Cloudflare AI Search falls back to local JSON search when no binding is present. The Ask AI route uses createConfiguredAskResponse, so missing AI Search, Workers AI, or OpenAI-compatible credentials fall back to the mock provider with local citations.

Use .dev.vars.example for environment names and keep real tokens out of the repository.