What you are looking at is a Bevy renderer compiled to WebAssembly, drawing through WebGPU.
Not a preview, not a cut-down web build. The same renderer runs in the editor, in play mode,
and in the game your players open.
Hierarchy, viewport, asset library and inspector. Nothing installed, nothing to license,
open on any machine you sign in from.
Everything else in the tab
Five more things the same browser session does.
Everyone in the same scene
Two editors that have received the same updates hold byte-identical state. No file locking, no last-save-wins, nothing to reconcile by hand. Work offline and the pending updates replay on reconnect.
Loro CRDT over WebSocket
Undo that outlives the session
Every change is an operation on the document, so the whole history stays queryable. Step back through it, branch from any point, or pin one version as the one players get.
Operation log, snapshots server-side
Code where the nodes run out
An editor sits beside the graph for the logic that is quicker to type than to wire, with the engine's API documented inline. Mix written scripts and node graphs in one project.
Scripts compile to WebAssembly
An assistant that reads your graph
The assistant receives the script you are working on, not just a prompt, and answers with a graph you can apply directly. Model credentials stay server-side.
Returns an applicable script
Publish to a link, not a store
Publishing pins the current version and lists the game in the launcher. Players open a link and they are in — no download, no store approval, no build to babysit.
Version pinned by content hash
Node graphs that compile, not interpret
Wire game logic from conditions, loops, operators, variables and error handling. The server
compiles the graph to WebAssembly, so the browser never ships a toy interpreter and a graph
runs in the same performance envelope as a written script.
SceneGameScriptingCompile
Nodes
Triggers
Control flow
Transform
Input
Maths
Variables
67 nodes across 12 categories, from triggers to trigonometry.
graph compiled server-side to WebAssembly
Everyone building with Horizon is in one room
No forum to search and no ticket queue. The editor, the engine and the people writing
both are in the same Discord.