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.
Environment
Kazzle injects a small set of platform variables into app processes. UI builds only receive values that are explicitly exposed at build time, such asVITE_* variables.
Process variables
| Variable | Description | Example |
|---|---|---|
PORT | The port your process should listen on | 3000 |
HOST | The host to bind to | 0.0.0.0 |
KAZZLE_API_KEY | API key for Kazzle-authenticated CLI and runtime calls from the process | kzl_... |
KAZZLE_API_URL | Base URL for the Kazzle API | https://api.kazzle.app |
PORT and HOST are always set for processes. KAZZLE_API_KEY is generated when Kazzle can issue an app-scoped key for that process.
Your process should bind to HOST:PORT. Kazzle handles preview routing and production domains on top of that.
Sibling component URLs
When an app has multiple components, Kazzle can inject URLs that let one component reach another:| Variable | Description |
|---|---|
COMPONENT_{NAME}_URL | URL for a sibling component at runtime |
VITE_COMPONENT_{NAME}_URL | Build-time sibling URL for Vite-based UI components |
name field: uppercased, non-alphanumeric characters become underscores. A sibling named API Server becomes COMPONENT_API_SERVER_URL.
These URLs point to the deployed sibling when one exists. Otherwise they point to the current development address for that sibling component.