Get started
Documentation
On this page
Kazari hosts static web pages. Claude, the CLI or the REST API publishes a page, and Kazari serves it at its own address on your domain, keeps every version, and retires it when you are done with it. Pick the path that fits what you want to do.
Key ideas#
Artifact : One page or site. It has a name, a description, an owner and a list of versions.
Slug : The artifact’s permanent short name, which becomes its address: the slug q3-report is served at https://q3-report.art.example.com/. Lower-case letters, digits and single hyphens, 3 to 63 characters. It cannot be renamed.
Version : An unchangeable snapshot of the artifact’s files. Every publish adds one. Version 3 always lives at https://q3-report--v3.art.example.com/.
Published version : The version served at the artifact’s main address. It is usually the newest, but rolling back points it at an older one without deleting anything.
Visibility : public pages appear in everyone’s listings; unlisted pages are left out of other people’s listings; unpublished takes the page offline without deleting it. Public and unlisted pages are both served to anyone who has the link.
Stale : A page marked for retirement. It keeps serving through a grace period, then it is soft-deleted (offline, restorable), later purged, and finally its slug becomes free again.
art.example.com stands for your instance’s domain throughout these pages.
Reference#
| Page | What is in it |
|---|---|
| MCP server | The twelve tools, resources, the publish-page prompt, chunked uploads, errors |
| CLI | Every kazari command and flag, output and exit codes |
| REST API | The user and admin APIs, wire types, limits and error codes |
| Configuration | Every YAML key, ${} environment references, .env, overrides |
| Sign-in and identity | OAuth for MCP clients, OpenID Connect providers, provisioning |
| Operations | Data layout, backup, upgrades, logs, metrics, jobs, quotas, abuse |
| Security | Threat model, origin isolation, headers, limits, operator checklist |