Kintsugi for Games
Kintsugi — “joining with gold” — is the centuries-old Japanese art of repairing broken ceramics with gold, turning damage into something worth more than the unbroken original. KilniX does the same for your back catalogue: the code and the assets you have already built, already paid for, and are no longer using. AI is the gold — the material that joins what you already own into a brand new, shippable mobile game. Not AI slop. Your code. Your assets. Work you have already paid for, becoming a new revenue line.
Every studio is sitting on years of finished work that earns nothing: shipped titles, cancelled projects, art libraries, tools, whole engines. It is paid for, it is yours, and it is idle. That is the raw material.
Provenance
The line ingests the art, code and design you own outright. Models are fitted to your material, per project, and the output carries your house style because it was made from it. There is no scraped corpus in the pipeline and nothing of anyone else's to answer for.
Your team
The material is work that already shipped, got cut, or never came off the shelf. Nothing here takes a live brief off an artist's desk — it puts the archive to work instead, so the people making new things carry on making new things.
The economics
Years of production sit at zero yield the day a project wraps. The line turns that inventory into playable mobile builds — new titles, built from paid-for material, at a fraction of what the original work cost to make.
A kiln is programmed as ordered segments: ramp to a target, then hold. This line has the same shape. Your catalogue goes in at the front, and every stage below writes a real file on the way — open any of them.
Genre data, competitor economics and retention comps go in. A design document comes out, with a stated fun hypothesis it can later be held to.
A person reads the document and answers one question: do I want this game to exist? Nothing is built until they do.
NoteNothing is built until a person says yes. On the headless path this gate blocks outright — an agent driving the line has nobody in the room, which is the exact case it exists for.
Scripts stand up a fresh repo and a Unity project, pull in every catalogued part the document calls for, wire the screens and stock the art.
NoteThe fire records its own assembly. Every part it placed and every art slot still open is written to fire-issues.json, so nothing about the build has to be taken on trust.
An AI director takes the assembled base and builds a prototype somebody can actually play — tuning feel, pacing and the first thirty seconds until there is something to judge.
The build is played and measured against a published rubric — seven weighted feel axes, a time-to-first-fun ceiling and a minimum number of reasons to come back.
NoteThe one stage with its own section on this site, because it is the one that decides whether a build is worth shipping.
Only once the gate passes: an overseer reads the full design document against the parts register, commissions a swarm to build what is missing, and gates their work before the assembler will touch it.
Assembly emits every tunable number as its own file — XP curves, drop tables, shop items, localisation. A designer edits them directly, or an agent does it over MCP.
Store listings are populated, the build goes out, and player data comes back to Balance with topline numbers to Ops. The loop closes.
NoteYou cannot rush the cooling. Work pulled from a kiln hot enough to touch cracks days later.
The hold at 900°C
A prototype is easy to produce and hard to judge, so the line does not leave the judging to opinion. Every build is played against a published rubric — seven weighted axes, a time-to-first-fun ceiling and a minimum number of reasons to come back — and the numbers land in a file you get with the build. Below is the bar, and a real firing measured against it.
| Axis | Weight | Score |
|---|---|---|
| First-30-Seconds Read | 1.5 | 7 |
| Game Feel / Juice | 1.5 | 6 |
| Power-Fantasy Arc | 1.3 | 8 |
| Build & Choice Depth | 1.2 | 8 |
| Moment-to-Moment Readability | 1.0 | 7 |
| Tension & Pacing Curve | 1.0 | — |
| Session Satisfaction | 1.0 | — |
| Weighted mean of what was scored | 7.2 / 4 bar |
Weights are DEFAULT_FEEL_AXES as the factory ships them. The mean is taken over the axes an evaluator actually scored — an unscored axis is excluded, never counted as a zero.
Measured on Hollow Reign, fired 11 August 2026: 7.2 on the feel rubric against a bar of 4, first genuinely engaging moment at 9 seconds against a ceiling of 30. The fastest to first fun of any firing so far.
Play the build these numbers came fromReal firings, with their receipts — parts placed, feel scores, time to first fun, build size. 5 are playable in your browser right now.
Dungeon delve with a sanctuary to return to. Seventeen pieces of art came out of the run, including the splash above.
Ten waves against a horde, ending at the Hollow King. Your kills rise as your soldiers. Nine seconds to first fun.
Age-of-sail naval command. Wind, range and a wall of orders — tack, beat to quarters, fire as she bears. Seven of seven parts placed and fifteen of fifteen screens built.
Isometric survivor on a broken stone field. Two seconds to first fun — the fastest of any firing — and the highest feel score the gate has returned.
Isometric voxel base-builder: gather, build, recruit, and hold the keep through a nightly horde. Fired from a raw brief with no design document, so the line read the intent and decided the rest.
Survivor inside a lit interior rather than an open field. Currently with the director.
Build in progress
Coming soon
The line, packaged as a product you run yourself. Eight surfaces, one pipeline — from training a model on your own art to a browser-playable build with its own repository.
The factory floor. Every stage, every asset and every build in one window.
The line in your pocket — approvals, art review and build status away from the desk.
The same surface in a browser, for anyone you need to bring in without an install.
Fit a model to your own art on your own hardware. Your references never leave the building.
Genre economics, retention comps and live market data on the desktop, feeding the design of every build.
A configured Unity project, assembled from the parts register and your assets.
Every build lands in its own repository, under your account, with its full history.
A playable browser build at the end of the run, so the thing can be handed round the same day.
A firing is booked and scoped against your own catalogue, and everything that comes back is a file or a build you keep.
Three to four weeks
Your material through the whole line once — code and assets in at the front, a playable mobile build out the other end. You see exactly how your catalogue behaves as raw material before committing a slate to it.
Six months, reviewed quarterly
The line runs continuously against your slate and your archive. Parts your games need get built into the register and stay there, and each model keeps learning your house style — so every firing starts warmer than the last.
Intakes open in cohorts, and each one is scoped to a handful of studios so the line runs properly against every catalogue in it. Join the waitlist and we will come to you before the next one opens.
