# Pyrix > Describe it — Pyrix builds it. Pyrix is an AI-native game editor: you build and personalize games by describing them in plain language, and Pyrix composes a declarative game document from vetted building blocks. No code is written, and none is generated. You approve every change. Games render with Pixi.js and WebGL at a smooth 60fps. Pyrix inverts how games get built. Instead of writing engine code, you author a **declarative game document** — a versioned, multi-file description of scenes, objects, behavior, assets, and audio that a pure-TypeScript ECS engine interprets at runtime. The document is the single source of truth: AI authors documents (never code), real-time collaboration syncs document state, and the Pixi.js/WebGL renderer is just a swappable projection of it — so your catalog outlives any one rendering library. Every change is auditable and reversible. AI proposes edits; you approve the consequential ones. Each edit is versioned, content-hashed, and appended to an audit log, with full local undo/redo. It runs on the edge (Cloudflare Workers + D1) with structured, secret-safe logging. ## Features - [AI Game Authoring](/#features): Describe a game in plain language and Pyrix composes it from vetted building blocks — assembling scenes, objects, and behavior. No code is written, and none is generated; the AI edits the document, so output is always valid and inspectable. - [Personalization at Scale](/#features): Seasonal skins, co-branded editions, and localized themes become a single AI-assisted edit to the game document. The marginal cost of a new variant collapses from a project to a prompt. - [No-Code Flow Editor](/#features): Author game behavior as a visual statechart — drag states, draw transitions, wire events to actions. Every edit is undoable and the flow lives in the document as the single source of truth. - [Human-in-the-Loop & Auditable](/#features): AI proposes document changes; you approve the consequential ones. Every edit is versioned, content-hashed, and recorded in an append-only audit log, with full local undo/redo — nothing changes your game without a trace. - [Real-time Collaboration](/#features): Humans and AI edit the same game document live, with per-entity conflict resolution, soft locks, and shared workspaces. Remote edits apply outside your local undo history, so per-actor undo stays coherent. - [Pixi.js / WebGL Performance](/#features): Games render with Pixi.js and WebGL for smooth 60fps playback. The rendering layer is a swappable projection of the document, decoupling your content from any single graphics library. ## How it works - **Declarative game document**: Versioned, multi-file, engine-interpreted. Scenes, game objects, the behavior flow, asset descriptors, and audio bindings all live in the document. AI and collaboration operate on document/state, never on generated code or serialized commands. - **Pure ECS engine**: A headless, framework-free TypeScript engine (components, systems, scene graph) with a full keyframe + bezier-easing animation system. The same engine runs in the editor, in the standalone runtime, and headless for AI and collaboration. - **Command-based editing**: Every reversible edit is a Command with an exact inverse, giving robust local undo/redo. Remote and AI changes apply through a separate path so they never pollute your history (per-actor undo). - **Agentic authoring**: A Claude Code plugin ships a scene MCP server, authoring agents, and a create-a-game skill, so an AI assistant can build and modify games directly against the document. - **Auth & multi-user**: Sign in with credentials, GitHub, or GitLab. Role-based access, group workspaces, invites, and share links — authorization is always derived server-side, never from client claims. - **Edge-native**: Deployed to Cloudflare Workers + D1 via OpenNext, with structured logging on every consequential operation and no secrets ever logged. ## Pages - [Home](/): Product overview and feature tour. - [Editor](/editor): The Pyrix game editor workspace — canvas, panels, timeline, flow editor, and AI authoring. - [Account](/account): Account and profile settings. ## Optional - [Privacy Policy](/privacy): How Pyrix handles your data. - [Terms of Service](/terms): Terms governing use of Pyrix.