Features
Static publishing features for Obsidian and Markdown sites.
KilnMD keeps generation local, validates the static output, and serves public sites from kilnmd.page or customer-owned domains.
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.
- 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
Notes as source
Obsidian and Markdown sites
KilnMD is built for Markdown-first notes, including Obsidian-style content, linked pages, attachments, generated indexes, and public documentation sets.
- Markdown-first publishing model
- Attachment and asset uploads through the manifest
- Works for notes, docs, research, and lightweight sites
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.
- Full and diff upload plans
- Immutable deployment records
- Atomic activation and retained rollback targets
Hostnames
Custom domains
Hosted sites stay on the public site boundary: default subdomains under kilnmd.page or customer domains pointed at customers.kilnmd.page.
- Default hosted sites on *.kilnmd.page
- Customer CNAME target at customers.kilnmd.page
- Dashboard-guided DNS instructions
Serving
Static performance
KilnMD keeps generated bytes in object storage and routes public requests through a lightweight serving path designed for static pages and assets.
- Immutable assets can be cached aggressively
- HTML can use short cache or revalidation behavior
- No server-side build work on public requests
Site experience
Search, graph, and themes
Interactive note-site experiences can still be static. Search indexes, graph payloads, CSS, and client scripts are uploaded as ordinary deployment assets.
- Static search index files
- Graph data and navigation payloads
- Theme CSS and client-side enhancements