Build & deploy

renku builds for Cloudflare Workers and Workers Static Assets. Bun bundles the application; the native TypeScript checker validates authored code before output is published.

On this page

Build and publish the generated output

The commands below deploy the docs workspace. For another app, use its directory and choose a unique worker.name in renku.config.ts. Authenticate the Cloudflare CLI with an account you control. The --prebuilt flag deploys renku's output without asking the CLI to detect a framework builder.

Terminal

# Build the app in this workspace.
bun run --cwd apps/docs build

# Install and authenticate the Cloudflare CLI.
bun add --global cf@1.0.0-beta.12
cf auth login

# Deploy the output produced by renku.
cd apps/docs
cf deploy --prebuilt

Inspect the result

The build writes .cloudflare/output/v0/: Worker modules, hashed browser entries, one stylesheet, public assets and deployment metadata. Workers Static Assets serves the immutable generated URLs. HTML responses use no-store. Failed builds remove incomplete output.

Develop with the same runtime

renku dev runs local workerd, watches templates, modules, tokens and config, then rebuilds and reloads the document. Build errors are visible and recover after a fix. Development uses full reloads; HMR and retained client navigation are not implemented.

Current scope

The current build supports one Worker with routes or a custom entrypoint, plus static assets. Client components are synchronous and have one ordinary HTML root. Keep async work on the server behind boundaries.

Bounded local-first sync is available; partial-query replication, retained routing and async client effect contracts remain future design work.

You can build Cloudflare output, inspect its assets and deploy it with the prebuilt workflow.

Return to getting started

← All guides · Explore the docs source (access required) →