
Kiln
8.4#3 in content management systemsFrom $4.99 a monthFree planWebAPISelf-hosted
Visit
| Fact | Kiln | plain |
|---|---|---|
| Content storage | Site files and their complete version history remain in the customer’s GitHub repository rather than a Kiln database. | Content is stored as Markdown files in a Git repository, with settings in a JSON file. |
| Integrations | Kiln works with GitHub repositories and hosts that redeploy on push, including Cloudflare Pages, Netlify, Vercel, and GitHub Pages. | The repository describes optional plugins for search, contact forms, reading time, forms sent to a configured backend, and GoatCounter page-view counts. |
| Intended users | Kiln describes itself for people who build static sites and want clients or other non-technical editors to update site content themselves. | The About page describes the browser admin as intended for people who would rather not use Git directly. |
| Publishing | Kiln supports drafts, scheduled publishing, named versions, history, and restoration, with publishes saved as Git commits. | Each save in the browser admin writes a commit to the repository, and older versions can be restored. |
No prices published.
Kiln suits people building static sites who want clients or other non-technical editors to update content themselves. It also fits owners who want edits retained in their own GitHub repository.
plain suits site owners who want to manage Markdown content in a browser while keeping content in Git. It also fits projects that want static output and a read-only JSON API.