Stop sketching.
Start authoring.
00One frame from the editor, exactly as the GPU drew it — VERIFIED · WASM. It looks like a screenshot. It isn't.
A structured document, not a canvas with features.
Files, pages, frames, components and design systems — authored through validated commands and rendered by a real engine.
The tree is the truth
Every node has one stable id and one parent, back-linked to its children. The authored document is canonical — the canvas is only a projection of it.
From clone to document in four commands
Get the code, bundle once, and open the design surface in the project you already work in.
Get the code
One repository. The document kernel, the renderer, and the design surface all build from it.
The useful answers, up front
A few honest answers about what Crafty is, where it fits, and how much of a toolchain it expects from you.
Is Crafty another design tool?
Crafty is a structured visual-authoring system with a renderer — not a canvas with features attached. Files, pages, frames, components and design systems are real document structures, and the Rust/WASM/WebGPU engine renders a resolved projection of them.
Does it execute my React or TSX components?
No. The browser slice models visual layers and states directly; it does not execute React/TSX components or mutate source files. What you author is a document with its own schema — which is what makes it durable, versioned, and renderer-independent.
What does WebGPU have to do with it?
The renderer is a custom Rust/WASM/WebGPU engine. It needs a secure origin — a loopback address in development, or HTTPS on your tailnet — and an iPad needs iPadOS 26 or newer. There is no fallback backend: if WebGPU is unavailable, that is a diagnostic, not a WebGL downgrade.
Can agents work in it?
Yes, and by design. Agents mutate the document through the same validated, invertible commands as humans — there is no separate agent-only mutation path. The session record shows every command, its validation, and its inverse.
How do I try it?
Clone the repository, bundle once, and run the desktop face — the design surface opens on a secure loopback origin in your browser. Files persist under ~/.crafty and survive restarts, so you can close and come back.
Give your agents a real document.
Structured files, validated commands, and a versioned record of every change — in a local surface you can leave running.