Local
$0/ month
Free in both cadences · sample
The CLI and a cache on your own disk. For one machine and one repo.
- Content-hashed task cache
- Restores on every local run
- Works offline
Build cache · CLI · for monorepos
Kiln: a build cache for monorepos
noun · kiln · /kɪln/
An oven that fires each piece once. Here: a fictional CLI that fingerprints every task in your monorepo, runs it once, and restores the output after that.
kiln run buildsampleSee sample pricingHow it fires
Three steps. Nothing fired twice.
Step 01: Hash
Kiln reads each task’s inputs (sources, lockfile, an env allow-list) and turns them into one fingerprint.
kiln hash build
Step 02: Fire
A fingerprint it has never seen runs the task for real, then stores the outputs and logs under that key.
kiln run build
Step 03: Restore
Same fingerprint next time, on a laptop or in CI: Kiln restores the outputs and replays the log instead.
kiln run build
Sample pricing
Free on one machine.
Billing cadence
Shared
$24/ month
Billed monthly · sample
A remote cache your whole team and CI restore from, priced per workspace.
- Everything in Local
- Remote cache for CI and laptops
- Per-branch cache scopes
Kiln is fictional. Prices are sample figures and nothing can be bought.
Brief answers
The short version.
No. Kiln is a fictional brand, and this page is a landing page example by CraftLayer Studio. There is nothing to download.
In the concept: the outputs and logs of any task you declare, keyed by a hash of its inputs.
No. The concept wraps the scripts you already have, so your package scripts stay the source of truth.
Source files, the lockfile, declared environment variables and the command itself. Change any of them and the task fires again.
On the Shared plan, in a hosted bucket scoped per workspace and branch. That plan, like its price, is a sample.
Yes, in the concept: kiln cache clear removes local entries. It is a sample command, not a real one.
Get started
Fire it once: see a sample first runA first run
Nothing to install.
Kiln is a fictional brand, so this demo ships no package. The session on the right is typeset to show how two runs of the same build would read: the first fires what is new, the second restores everything.
TerminalSample session
$ kiln run build --filter=web hashing 3 packages · sources, lockfile, env allow-list @example/ui miss → firing @example/utils hit ← restored @example/web miss → firing stored 2 entries in .kiln/cache $ kiln run build --filter=web @example/ui hit ← restored @example/utils hit ← restored @example/web hit ← restored nothing to fire · 3 of 3 restored