Semantic WebGPU compiler · You own the code

Describe a game.
Get the code.

Lud Engine writes your game as real Three.js on a production WebGPU runtime, runs what it writes, checks the result, and hands you an editable scene and every line of source. Prompt in, full editor out. We compete on how much control the creator keeps.

Visit Lud Engine

❖

Self-verifying build loop

The engine runs what it writes, inspects the result with vision and automated checks, and fixes it before it reaches you.

Runs and inspects its own builds
Every step is inspectable and reversible
Agents coordinate per file, no clobbering

⎈

Creator control

Prompt first, full control after. Viewport, Game Graph, code: every surface stays editable.

Live viewport and the Game Graph for fast iteration
Custom editor tabs the studio authors for its own game
Two people and their agents on one project, live

◈

Grounded agents

The agent framework reads your design docs, so generated systems match the game you're actually making.

Generation that reads the design doc
Tell it once; the whole workspace knows
Design intent carried into every system it writes

✦

Own it outright

Real Three.js with Rapier physics and no engine ceiling. Full source and a self-contained playable exported on every plan, including free.

Custom TSL / WGSL shaders, any npm package, glTF
Download your source on every plan, host anywhere
Desktop apps for Windows and macOS, native mobile builds

Lud AI · In Engine

One assistant that works everywhere and remembers.

It opens with a keystroke in any Lud product and already knows the studio. Ask a question and it answers from your real data. Ask for the work and it builds the scene.

It never has more access than you do. Not by policy, by construction.
Hand it as much control as you want. Every change is recorded and revertible.

“Add a grappling hook to the scene.”

Builds it in the running game, with the design doc already in context.

Engine proof