Private beta · v0.1
An AI collaborator that can see your Unity scene.
Demiurge pairs a frontier model with Unity-specific scaffolding — scene perception, action verification, a growing Unity 6 reference library — so the code it writes actually runs in your editor instead of hallucinating past APIs.
The gap
Generic AI tools don't know your editor.
ChatGPT and Copilot can't see your scene, can't open the Unity editor, and can't tell you whether the C# they just wrote compiled. They guess from text alone, often against training data that predates Unity 6.
The result is code that looks right — _Color instead of _BaseColor, PostProcessVolume instead of the URP Volume framework, method signatures that quietly moved two versions ago. It compiles. It runs. It doesn't do what you asked.
Closing that gap isn't about training a better model. It's about wrapping the model in the right scaffolding: look at the scene, verify the change, consult the real docs, learn from what went wrong. That's Demiurge.
Why it works
The difference you'll actually feel.
Every Unity developer who's tried ChatGPT or Copilot knows the failure modes. Demiurge closes them.
Code that runs the first time
“It compiled — but it didn't do what I asked.”
Demiurge writes code against what’s actually in your editor: your render pipeline, your packages, your scene. Far fewer scripts that look right on paper and fail silently in practice.
Current Unity, every time
“That method hasn't existed since Unity 2021.”
Generated C# targets the Unity version you’re actually running. Current APIs only — no method signatures that moved two versions ago, no deprecated URP boilerplate, no reliance on the model happening to remember recent changes correctly.
Safe to experiment
“Wait — what did that just do to my scene?”
Nothing runs without your explicit approval. Every change is cleanly reversible with a single keystroke. Experiment on real scenes without the anxiety of half-applied modifications or orphaned objects.
In practice
Type what you want. See it happen.
You
“Create a hill in the center of the scene.”
Demiurge
- 1. Briefing confirms URP + Unity 6. Reference retriever surfaces
terrain.md. - 2. Multi-angle BEFORE screenshot captured.
- 3. Script written using
Terrain.CreateTerrainGameObject, heightmap with a smooth Gaussian falloff, registered for undo. - 4. AFTER screenshot + hierarchy diff. Claude verifies the hill is centered and visible. Verdict: Verified.
All in one chat turn. Ctrl+Z rolls it back if you change your mind.
Your project stays yours.
Session logs split into private (everything — scripts, screenshots, paths, scene names — never leaves your machine) and shareable (categorical signals only, built from an explicit allow-list, opt-in to transmit). Screenshots are always private. No implicit telemetry.
Read the privacy policy →One bill. No surprises.
Pick a plan, pay the flat monthly price, and everything the scaffolding uses is included — briefing, verification, reference retrieval, the model calls themselves. No per-turn charges, no end-of-month surprise from a separate invoice. Cancel any time; next period drops you back to Free.
See the four tiers →Stop fighting your AI. Start shipping Unity.
Free to try. Your first hill, light rig, or material swap is one prompt away.