Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kazzle.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Components

Components are the executable parts of your app. Each component has a type that determines how it runs.

​
UI components

A UI component is a web frontend — React, Vue, Svelte, plain HTML, or any framework that serves on a port. 
{ name: 'Dashboard', type: 'ui', path: '.', lifecycle: { dev: 'bun run dev' } }
  • Max 1 per app — Kazzle assigns a single preview URL per app
  • lifecycle.dev — command for the dev server (used by “Start preview”)
  • lifecycle.build — command to build for production deploy
  • lifecycle.run — command to serve the production build
If lifecycle.dev is not set, the preview system falls back to detecting common dev servers (Vite, Next.js, etc.).

​
Process components

A process component is a backend service, worker, or scheduled task. 
{ name: 'API', type: 'process', path: './server/index.ts' }

​
Persistent processes

The default mode. The process runs continuously.

​
Cron processes

Add a schedule field with a cron expression: 
{ name: 'Cleanup', type: 'process', path: './jobs/cleanup.ts', schedule: '0 * * * *' }

​
Triggered processes

Add a trigger field: 
{ name: 'Webhook handler', type: 'process', path: './webhooks/handler.ts', trigger: 'webhook' }

​
Chrome extensions

{ name: 'My Extension', type: 'chrome-extension', path: './extension' }
Chrome extensions are always local — they run in the user’s browser, not on Kazzle’s infrastructure.

​
Lifecycle commands

PhaseWhen it runsExample
devDuring draft previewbun run dev, vite, next dev
buildBefore remote deploybun run build, vite build
runIn productionbun run start, node dist/server.js