Markdown site publishing

KilnMD

Publish Obsidian and other Markdown-based note sites from static output generated in the browser or local Kiln client. The platform receives files ready to host, not a server-side plugin build job.

Local or browser generation Verified static deployment output kilnmd.page and customer-domain serving
KilnMD dashboard showing sites, deployment status, and account navigation
Marketing
kilnmd.com

Static Astro site on a dedicated Cloudflare Pages project.

Dashboard and API
dashboard.kilnmd.com

Authenticated app, billing, account management, and publish API.

Hosted sites
*.kilnmd.page

Default public site hostnames served by the public Site Worker.

Custom-domain target
customers.kilnmd.page

CNAME target for customer-owned hosted-site domains.

Workflow

Publish static output, then serve it from the public plane.

KilnMD validates deployment files and activates immutable releases. The expensive work of turning notes into a site happens before upload.

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.

Features

Built for public note sites and documentation.

All features
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.
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.
Performance
Serve static output from Cloudflare-native storage, routing, and cache layers.
Search and themes
Ship static search indexes, graph data, and theme assets with the deployment.
Privacy-forward

A hosting boundary that respects how note sites are made.

The public platform stores and serves the generated site. It does not need private vault internals or server-side execution of user plugins.

Static publish boundary
KilnMD receives output intended for public hosting, not private vault internals.
Immutable deployments
Every publish is a versioned deployment that can be validated before activation.
Separate site domain
Hosted sites stay on kilnmd.page or customer-owned domains.
Client-side experiences
Search, graph, and theme assets can ship as static files.
Questions

Common boundaries

KilnMD keeps the marketing site, dashboard/API, hosted sites, and custom-domain target explicit.

Publish your first Markdown site.

Start with Core, then add custom domains and larger quotas when you need them.