Apps are products Kazzle builds for you. You describe what you want, the AI builds it, and you keep refining by chat. A simple app might be a web page or a Chrome extension. A bigger one can have a backend, automations, and a database.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.
App vs component
An app is the whole project. A component is one piece inside it.The four parts
UI is what people open and click through. Examples: landing pages, dashboards, internal tools. Process does work in the background. Examples: API routes, webhook handlers, scheduled jobs, auth. Skill is a tool the AI can call from a conversation. Examples: pulling data from a service, transforming files, running a workflow. Database is created on demand. When your app needs one, the AI sets up a dedicated Postgres instance and stores credentials in the vault. Databases are not declared inkazzle.config.ts — they’re provisioned through the db tool in a thread.
Common app shapes
| App shape | Parts | Example |
|---|---|---|
| Simple website | UI | Landing page, brochure site |
| Internal tool | UI | Dashboard, admin tool |
| Chrome extension | UI | Tab manager, page annotator, productivity tool |
| Backend service | Process | API, worker, webhook receiver |
| AI tool | Skill | A reusable tool for the AI |
| Full app | UI + Process | Customer portal, SaaS product |
What every app gets
| Included | What it means |
|---|---|
| Source code | Git repo managed in Kazzle |
| Dev preview | Live preview in the app tab while the AI builds |
| Deploy to production | Deploy to Kazzle’s hosting for a public URL |
| Database | Dedicated Postgres, provisioned on demand |
| Secrets vault | Encrypted storage for API keys and credentials |