kiln-cms app on your repo. Allowlisting is gated to whoever runs the shared worker, which is us. A self-serve add-site flow is the next thing we're building; until it ships, the steps below are how onboarding actually happens.
1Get your site Kiln-ready and hosted
This part is the same as self-host and you do it yourself: push your static site to a GitHub repo, connect a host that auto-deploys on each commit (Cloudflare Pages recommended, free and commercial-friendly), and annotate what is editable with data-cms attributes plus the two script tags. An AI can do the annotation from KILN_PROMPT.md. The self-host steps spell this out.
2Send us the repo and the site URL
Open an onboarding issue or email us with your repo and your live site URL. We allowlist your origin on the shared worker and send you the install link for our kiln-cms GitHub App.
3Install our app on your repo, one click
You click Install, choose Only select repositories, and pick your site's repo. That is the only button you press. Our app can only ever touch the repo you select. You point your site's config at our shared worker (we give you the one line), and you're on.
4Sign in and edit
Visit yoursite.com/kiln and sign in. Editing, publishing, history, drafts, scheduled publishing, and Google sign-in for your editors all run against our worker. You did not deploy or maintain anything.
kiln-cms app installed on your repo, not a fresh app you registered. That is the one thing that differs from self-host, where the app is yours.
You run none of the plumbing, and still own your content.
We run the worker and the app; your repo and host stay yours; your pages are plain HTML you can take anywhere. Want zero setup, hosting included? Fully managed runs everything. Want to run it all yourself for free? Self-host. Ask us to onboard your site.
Kiln