Local generation

Browser-local rendering

KilnMD starts at the static publish boundary. Markdown, Obsidian content, and theme/plugin work are rendered locally or in-browser, then the platform receives the verified output tree.

Create account Read docs

What this means

Generate the site in your browser or Kiln client before anything is uploaded.

No server-side execution of vault plugins
Static HTML, assets, and manifests are the publish artifact
Full and diff publish flows fit browser or desktop clients

A clear trust boundary

The hosting platform validates files and metadata, but it does not run arbitrary user code to produce the site.

Portable output

The output is an ordinary static file tree, which keeps serving simple and makes deployments easy to inspect.

Repair-friendly publishes

Clients can send a full mirror when local state is uncertain, or send a diff when the previous deployment is trusted.

Proof points

Designed around static site operations.

Local/browser generation

Manifest validation

Static output only

Related features

Each feature keeps the same local-generation and static-hosting boundary.

See plans

Obsidian Markdown

Publish from Obsidian vaults and other Markdown-based knowledge bases.

Workflow

Upload, verify, and activate immutable deployments instead of overwriting live files.

Custom domains

Start on kilnmd.page, then attach customer-owned domains when you are ready.