Skip to content

Kiln documentation

Nine pages so far. They come from the product repository, written by whoever ships the surface, and every claim in them is traced to the code rather than to the marketing site.

Surface pages describe one part of the product in full, for somebody who has not got it open. The in-app help panel beside each surface is the short version for somebody who has; these are the thorough version, and neither is a copy of the other.

  • Connections reaching a system that is not Kiln
  • Secrets where secret values live and who may manage them
  • App clients credentials for something calling in
  • Inboxes an email address Kiln watches
  • Registers governed reference data your organisation owns
  • Datasets small authored tables a flow reads at run time
  • Test centre proving a change before it goes live
  • Experiments two versions over the same records
  • Monitoring what a snapshot is computed from

Guides run end to end across several surfaces, which is the thing no single screen can explain, because none of them knows where you came from.

Reference is looked up rather than read, and these two are generated from the platform’s own declarations, so they cannot drift from what it does.

Explanation is read away from the keyboard.

People and roles, six more guides, three more generated reference pages, the generated reference, and the tutorial. The surface pages came first because writing them is what found four authorisation gaps in the product, which is a better argument for their priority than tidiness was.