Artifacts, on a server you own.
Cloud version coming soon, feel free to self host now.
Join the waitlist
Submitting opens a confirmation page on our list server. Confirm from your inbox and you are on the list. One email when Cloud opens, and you can leave from any of it.
You
Publish the churn report you just built, and keep it private.
Claude
Claude
Publishing it now, private visibility.
Tool call
{ type: "html", slug: "churn-jul", visibility: "private" }
→ https://kiln.acme.dev/a/churn-jul-a4f9c2
Claude
Done. It is live, and private, so only key holders can open it.
kiln.acme.dev/a/churn-jul-a4f9c2One tool call. No pasted markup.
- .html
- .jsx / .tsx
- .md
- .zip
- Node 22, or one container you build. No build step for the artifact itself
- Plain files under /data by default. Point it at S3, git, Postgres, or SQLite instead
- Private by default, unguessable slug, scoped keys, MIT
Self-hosting stays the full product. Cloud will sell the operating work, never features held back from the open source build. If the hosted version stops being worth it, the artifacts are files, and moving them is a copy.