GraiEngine

AI that you control

AI in GraiEngine is a core editor subsystem, not a plugin bolted on afterwards. Every change flows through typed, validated operations. Each one can be previewed, and each one can be reversed. If a group of changes fails part-way through, the whole group rolls back.

That is the point of the design: the person building the game stays in charge of what changes, and can see what changed before it stays.

From idea to a playable scene, in four steps

1. Planning. Describe the game idea. The AI puts together a structured plan with scenes, assets, and gameplay systems.
2. Concept art. Generate or pick concept images for each asset from the built-in library. Approve, reject, or refine them until they match what you had in mind.
3. 3D generation. Approved concepts are converted to GLB models and brought into the asset pipeline automatically.
4. Scene assembly. Terrain, water, lighting, entity placement, and gameplay scaffolding are assembled and ready to play.

After assembly, you can keep working in the editor, or start another scene.

Assets, your way

Bring your own artwork, sketches, or reference images, and the pipeline turns them into textured 3D models for the scene. If you do not have assets yet, the built-in library has models, textures, and materials to start from. Every asset is imported as a GLB model, optimised and ready to place.

Built on Bevy and Rust

GraiEngine is built from the ground up on Bevy's entity component system and Rust. Rust compiles to native code, with no garbage collector and no runtime overhead. Bevy's architecture is made for data-oriented design and parallel systems. Rhai scripting is built in, lightweight and sandboxed, so game logic can be written and changed without recompiling. Blueprint graphs give the same logic in visual form, for people who prefer graphs to code.

Status: GraiEngine is in active, early development. Details on the engine's own site are the current record: graiengine.com.