A closer look at the Crucible: what changes when a build moves from hosted-only to forged and owned, how a firing actually runs start to finish, and straight answers on owning it outright.
Built on a Pickaxe? Smelter is the Crucible, shaped for Pickaxe makers
The Wolf · on it
A hosted tool and a forged product are not the same thing wearing different clothes. Here is what actually changes, not just what the pitch says changes.
A raw code export can hand you a folder that will not start without a rebuild. A Crucible build runs the moment you unzip it.
Describe what you want to exist. The five checks run against it and come back with plain verdicts and the questions they could not answer on their own. You answer those, or you decide to carry them as known risk. It is a conversation, and it is short.
What survives becomes a signed plan: the problem, the scope, the non-goals, the risks you accepted. You sign it. That is the thing the build is measured against later, which is why it exists at all.
The forge builds it in front of you, step by step, on the screen. It burns its own hosted key, not yours. Nothing you type here is an API credential.
Six gates run, and the assay measures the finished build against your signed plan. If it passes, you choose your door: take the whole thing and own it, or let the forge keep running it. If a gate goes red, the screen tells you which and why, in words, and the next move is yours: fix and refire, or sign and take it.
Any gate can be signed past, knowingly. Decide the risk is worth carrying, put your name to it, and the build is yours; the decision rides in the papers that travel with it.
Five minutes from here to a build you own, or one we host for you. Bring the idea, or bring what you already built.
Firings run in small batches. Leave your email and the invitation lands there when your place opens. Nothing to install; the build is yours to keep.
Already invited, or already a member? Sign in at the forge