Game Engines — procurement report
ProductArena · rankings as of 2026-09-15 · evidence as of 2026-09-15 · 8 products · 56 judged requirements · 448 judged cells
Methodology: Every product is judged against a shared taxonomy of user stories using cited evidence — hands-on probes > repository code > independent community sources > vendor claims — never opinion. Full writeup: https://ultrametric.ai/productarena/methodology
Leaderboard
| # | Product | PA Score | Coverage score | Applicable cells | Confidence |
|---|---|---|---|---|---|
| 1 | Babylon.js | 31.7 | 32.7 | 47/56 | B |
| 2 | Phaser | 31.4 | 28.8 | 48/56 | C |
| 3 | PlayCanvas | 26.9 | 28.0 | 54/56 | B |
| 4 | Unity | 25.6 | 29.8 | 53/56 | B |
| 5 | Godot Engine | 22.5 | 32.6 | 50/56 | B |
| 6 | three.js | 22.2 | 22.8 | 47/56 | C |
| 7 | Bevy | 15.3 | 19.7 | 47/56 | C |
| 8 | Unreal Engine | 15.2 | 20.4 | 52/56 | B |
PA Score = agent-readiness blend (see methodology). Coverage score = weighted share of judged requirements met. Confidence = how much of the score rests on tested vs claimed evidence (A–D).
Uncertainty note
The current #1/#2 gap in this arena is not close enough to qualify for the multi-judge uncertainty pass (or the pass has not covered it yet) — no extra caveat applies beyond the per-product confidence grades above.
Buyer checklist (RFP)
The arena's 56 judged user stories as requirements, grouped by theme. Priorities mirror the story weights our scoring uses (3 = must-have, 2 = should-have, 1 = nice-to-have). Interactive version with per-requirement verdicts for the top products: /arena/game-engines/checklist
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
- ai-native userPlug MCP servers into this product so it can use their toolsmust-have
- ai-native userConnect an agent via an official MCP servermust-have
- ai-native userDrive the product through a documented public APImust-have
- ai-native userDelegate tasks to a built-in AI assistant inside the productmust-have
- ai-native userPoint an agent at llms.txt or agent-oriented docsshould-have
- ai-native userRun the product headlessly / in CI for automationshould-have
- ai-native userUse an official CLIshould-have
- ai-native userIssue scoped/least-privilege API credentials for an agentshould-have
- ai-native userBuild against official SDKsshould-have
- ai-native userSubscribe to events via webhooksshould-have
- ai-native userGet AI-generated insights and suggestions from my data inside the productshould-have
- ai-native userSet up automations that run autonomously in the backgroundshould-have
- ai-native userOperate the product with natural-language commandsshould-have
- ai-native userExplore an interactive API reference with runnable examplesshould-have
- ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)should-have
- ai-native userRely on versioned APIs with a documented deprecation policyshould-have
- ai-native userTest against a sandbox environment without touching production datanice-to-have
Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
- ai-native userAn agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interfacemust-have
- ai-native userLLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seenshould-have
- ai-native userAn official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assetsshould-have
- game developerRun ML models inside the game — an official inference runtime for on-device model executionnice-to-have
Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline
Getting content in — automated import, formats, marketplaces
- technical artistStandard interchange formats — glTF, FBX, USD — import cleanlyshould-have
- technical artistAsset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each oneshould-have
- game developerA large asset store or package ecosystem gives me ready-made models, tools, and pluginsshould-have
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
- ai-native userDefine rules that trigger actions automatically on eventsmust-have
- ai-native userPerform bulk operations across many items at onceshould-have
- ai-native userSchedule recurring jobs or workflowsshould-have
- ai-native userVersion, review, and roll back my automationsnice-to-have
Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine
The engine core — rendering, 2D, physics, performance at scale
- game developerThe engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processingmust-have
- game developer2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthoughtshould-have
- game developerProfile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavyshould-have
- game developerBuilt-in physics — rigid bodies, collisions, raycasts — works out of the boxshould-have
Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling
The editor as a product — scene tools, extensibility, team workflows
- technical artistA full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levelsmust-have
- game developerExtend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmaticallymust-have
- studio leadThe project format and tooling play well with version control and multi-person teams — mergeable scenes, diffable text formats, or built-in collaborationshould-have
Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automation
The engine without a human — CLI builds, CI test runs, dedicated servers
- game developerBuild and export the project from the command line, headless, in CI — no human clicking an editormust-have
- game developerGame logic runs headless on servers — a dedicated-server or server-runtime build without renderingshould-have
- game developerTests run headlessly — unit and integration tests of game code execute in CI against the real engineshould-have
Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness
The terms you build on — licenses, royalties, source access, pricing stability
- studio leadThe license is permissive with no royalties or per-install fees — I keep what my game earnsmust-have
- game developerRead and modify the full engine source when I hit a wallshould-have
- studio leadThe pricing and license terms have a track record of stability — no retroactive changes that reprice games already shippedshould-have
- studio leadThe project's governance and funding are transparent — a foundation, published finances, or a public roadmap I can plan againstnice-to-have
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
- ai-native userExport all of my data in open formats and leavemust-have
- ai-native userSelf-host the core productmust-have
- ai-native userDo everything through the API that I can do in the UIshould-have
- ai-native userRead the product's source under an open licenseshould-have
Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export
Shipping everywhere — desktop, mobile, console, browser payloads
- studio leadOne project exports to desktop, mobile, and (directly or via partners) consolesmust-have
- web developerMy game runs in the browser with a reasonable payload — WebGL today, and a credible WebGPU storyshould-have
- web developerThe engine installs from a package registry into my existing toolchain — a library I import, bundle, and tree-shake like any dependencyshould-have
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
- ai-native userPrevent my data from being used to train AI modelsmust-have
- ai-native userChoose where my data is stored (region/residency)should-have
- ai-native userControl data retention and deletionshould-have
- ai-native userOpt out of telemetry and usage trackingshould-have
Scripting — writing the game — languages, visual scripting, iteration speedScripting
Writing the game — languages, visual scripting, iteration speed
- game developerThe primary scripting language is productive and fully exposes the engine API, with a debugger behind itmust-have
- game developerThe edit-run loop is fast — hot reload or near-instant preview after a script changeshould-have
- technical artistBuild gameplay logic with visual scripting without writing codeshould-have
Appendix: recorded probes
Hands-on probe recordings — transcripts/videos a human can replay, the strongest evidence tier. Watch them at https://ultrametric.ai/productarena/proofs
- Babylon.js
curl -s https://doc.babylonjs.com/llms.txt | head -4terminal · recorded 2026-09-15 · exit 0 - Babylon.js
npm view @babylonjs/core versionterminal · recorded 2026-09-15 · exit 0 - Bevy
cargo search bevy --limit 3terminal · recorded 2026-09-15 · exit 0 - Bevy
curl -s -A "productarena-probe" https://crates.io/api/v1/crates/bevy | grep max_stable_versionterminal · recorded 2026-09-15 · exit 0 - Godot Engine
curl -s 'https://godotengine.org/asset-library/api/asset?godot_version=4.3&max_results=2'terminal · recorded 2026-09-15 · exit 0 - Godot Engine
brew info --json=v2 godot | grep descterminal · recorded 2026-09-15 · exit 0 - Godot Engine
curl -s -o /dev/null -w "HTTP %{http_code}" https://godotengine.org/llms.txtterminal · recorded 2026-09-15 · exit 0 - Phaser
npm view phaser versionterminal · recorded 2026-09-15 · exit 0 - Phaser
curl -s -A "Mozilla/5.0" https://phaser.io/llms.txt | head -3terminal · recorded 2026-09-15 · exit 0 - PlayCanvas
curl -s https://developer.playcanvas.com/llms.txt | head -6terminal · recorded 2026-09-15 · exit 0 - PlayCanvas
npm view @playcanvas/editor-mcp-server versionterminal · recorded 2026-09-15 · exit 0 - PlayCanvas
npm view playcanvas versionterminal · recorded 2026-09-15 · exit 0 - three.js
curl -s https://threejs.org/docs/llms.txt | grep -m1 Instructionsterminal · recorded 2026-09-15 · exit 0 - three.js
npm view three versionterminal · recorded 2026-09-15 · exit 0 - three.js
curl -s https://api.npmjs.org/downloads/point/last-week/threeterminal · recorded 2026-09-15 · exit 0 - three.js
curl -s https://threejs.org/llms.txt | head -6terminal · recorded 2026-09-15 · exit 0 - Unity
brew info --json=v2 unity-hub | grep descterminal · recorded 2026-09-15 · exit 0 - Unity
curl -s https://unity.com/llms.txt | head -4terminal · recorded 2026-09-15 · exit 0 - Unreal Engine
curl -sL -o /dev/null -w "%{http_code}" https://raw.githubusercontent.com/EpicGames/UnrealEngine/HEAD/README.md; curl -s -o /dev/null -w "%{http_code}" https://www.unrealengine.com/en-US/licenseterminal · recorded 2026-09-15 · exit 0
Cite as: ProductArena by Ultrametric Inc, Game Engines arena, rankings as of 2026-09-15 — https://ultrametric.ai/productarena/arena/game-engines
License: © 2026 Ultrametric Inc. Brief quotation of individual verdicts, scores, or evidence excerpts is permitted with attribution to "ProductArena by Ultrametric Inc (ultrametric.ai/productarena)", as is use of the data to evaluate, contest, or contribute corrections. Bulk copying, redistribution, or use to build competing datasets requires prior written permission (see DATA-LICENSE in the repository).
No liability: rankings, verdicts, and scores are research outputs derived from the cited evidence at a point in time, provided "as is", without warranties. Ultrametric Inc accepts no responsibility for procurement, purchasing, or other decisions made in reliance on them — verify against the cited evidence before acting (https://ultrametric.ai/productarena/terms).