Deployments

Publishing workflow

KilnMD treats every publish as a versioned deployment. The platform verifies upload state before activation, then public traffic moves to the new manifest.

Create account Read docs

What this means

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

Full and diff upload plans
Immutable deployment records
Atomic activation and retained rollback targets

Upload plans

The client asks the control plane what to upload, sends only required files, and keeps the final deployment path set explicit.

Verification before serving

Paths, file sizes, content types, and hashes are validated before a deployment can become active.

Activation by pointer

Public traffic changes by switching the active deployment pointer, not by mutating files under a live route.

Proof points

Designed around static site operations.

Full publish

Diff publish

Rollback-ready

Related features

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

See plans

Browser rendering

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

Obsidian Markdown

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

Custom domains

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