KKilnMD
Publish guide

Documentation

KilnMD receives already-generated static output. Use these notes to understand what crosses the publish boundary and how public sites are served.

Create account Pricing
Publishing boundary
Generation happens locally or in-browser. The platform receives a static output tree plus manifest metadata, validates the result, and stores public files.
Deployment lifecycle
A deployment moves from upload planning through verification before it can become active. Public serving uses the active deployment pointer.
Hostnames
Marketing, dashboard, hosted sites, and custom-domain targets are split across separate hostnames to keep user content away from app cookies.
Lifecycle

The publish path

The dashboard and API coordinate upload planning, verification, and activation.

Generate locally
Kiln renders Markdown, Obsidian content, themes, and client-side assets in the browser or local client.

This stage keeps the product static-first: content generation and public serving are deliberately separate responsibilities.

Related

Useful next pages for this topic.

Publishing workflow
Full and diff publishes, validation, and activation.
Open page
Custom domains
Default hosted domains and the customers.kilnmd.page target.
Open page
Security model
How the control plane and public site plane stay separate.
Open page