Your agent made a page. Host it somewhere you own.

Dropkiln takes HTML, a single React component, Markdown, or a zipped site and returns a link nobody can guess. You run it as one container on a server you control.

What happens to a file Waitlist for the hosted version

Publish

$ curl -sX POST $KILN/api/artifacts \
   -H "Authorization: Bearer $KEY" \
   -d '{"type":"html","content":"<h1>Q3</h1>"}'

201 {
  "slug": "k4m9x2p7qw",
  "url": "https://kiln.acme.dev/a/k4m9x2p7qw?k=…",
  "visibility": "private"
}

Private is the default, so the link carries its own grant. Rotate it later and the old one stops resolving.

Three things happen to a file. Nothing else does.

It arrives

An agent calls one MCP tool. You can also drop the file on the dashboard or send it through the CLI. Dropkiln serves the file you handed it, so there is no build step between you and the link.

It gets fired

The artifact lands on disk as ordinary files under /data. Backing it up means copying that directory. If you would rather keep artifacts elsewhere, the same server writes to S3, git, Postgres, or SQLite instead.

It comes back as a URL

The slug is unguessable and every page carries noindex, so the link reaches the people you hand it to and nobody else. Rotate the signed link when you want it to stop working, put a password on it, or make it public on purpose.

Run it yourself today

The server is MIT and already public. There is no queue for this one and no feature held back behind a plan.

Runs on bare Node 22, or as one container you build
No database by default. Plain directories on disk
Private by default, with scoped API keys for agents

Read the source

The hosted version, when it opens

Cloud will run this same server for you. The plan is custom domains, backups, and updates applied without your involvement. It has not opened yet, and the waitlist is how you hear that it did.

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.

Self-hosting stays the full product. Cloud sells the operating work, never features taken out of the open source build. If the hosted version ever stops being worth it, the artifacts are files, and moving them is a copy.