Skip to content

Game Engines Arena

Game Engines arenaBuyer checklist

Every requirement we judge game engines products against, as a ready-to-send RFP checklist — with each item's priority, why it matters, and how the top-ranked products score on it today.

56 requirements · 12 themes · verdicts for 8 products · updated 2026-09-15 · priorities mirror the story weights our scoring uses (methodology)

Procurement report →
Show the markdown export
# Game Engines — buyer checklist (RFP)

Derived from ProductArena's evidence-graded user-story taxonomy for Game Engines: 56 judged requirements. Priorities mirror story weights (3 = must-have, 2 = should-have, 1 = nice-to-have).

## Agenticness

- [ ] **[must-have]** Plug MCP servers into this product so it can use their tools
- [ ] **[must-have]** Connect an agent via an official MCP server
- [ ] **[must-have]** Drive the product through a documented public API
- [ ] **[must-have]** Delegate tasks to a built-in AI assistant inside the product
- [ ] **[should-have]** Point an agent at llms.txt or agent-oriented docs
- [ ] **[should-have]** Run the product headlessly / in CI for automation
- [ ] **[should-have]** Use an official CLI
- [ ] **[should-have]** Issue scoped/least-privilege API credentials for an agent
- [ ] **[should-have]** Build against official SDKs
- [ ] **[should-have]** Subscribe to events via webhooks
- [ ] **[should-have]** Get AI-generated insights and suggestions from my data inside the product
- [ ] **[should-have]** Set up automations that run autonomously in the background
- [ ] **[should-have]** Operate the product with natural-language commands
- [ ] **[should-have]** Explore an interactive API reference with runnable examples
- [ ] **[should-have]** Download a machine-readable API spec (OpenAPI or equivalent)
- [ ] **[should-have]** Rely on versioned APIs with a documented deprecation policy
- [ ] **[nice-to-have]** Test against a sandbox environment without touching production data

## Ai workflows

- [ ] **[must-have]** An agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interface
- [ ] **[should-have]** LLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seen
- [ ] **[should-have]** An official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assets
- [ ] **[nice-to-have]** Run ML models inside the game — an official inference runtime for on-device model execution

## Asset pipeline

- [ ] **[should-have]** Standard interchange formats — glTF, FBX, USD — import cleanly
- [ ] **[should-have]** Asset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each one
- [ ] **[should-have]** A large asset store or package ecosystem gives me ready-made models, tools, and plugins

## Automation depth

- [ ] **[must-have]** Define rules that trigger actions automatically on events
- [ ] **[should-have]** Perform bulk operations across many items at once
- [ ] **[should-have]** Schedule recurring jobs or workflows
- [ ] **[nice-to-have]** Version, review, and roll back my automations

## Core engine

- [ ] **[must-have]** The engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processing
- [ ] **[should-have]** 2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthought
- [ ] **[should-have]** Profile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavy
- [ ] **[should-have]** Built-in physics — rigid bodies, collisions, raycasts — works out of the box

## Editor tooling

- [ ] **[must-have]** A full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels
- [ ] **[must-have]** Extend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically
- [ ] **[should-have]** The project format and tooling play well with version control and multi-person teams — mergeable scenes, diffable text formats, or built-in collaboration

## Headless automation

- [ ] **[must-have]** Build and export the project from the command line, headless, in CI — no human clicking an editor
- [ ] **[should-have]** Game logic runs headless on servers — a dedicated-server or server-runtime build without rendering
- [ ] **[should-have]** Tests run headlessly — unit and integration tests of game code execute in CI against the real engine

## Licensing openness

- [ ] **[must-have]** The license is permissive with no royalties or per-install fees — I keep what my game earns
- [ ] **[should-have]** Read and modify the full engine source when I hit a wall
- [ ] **[should-have]** The pricing and license terms have a track record of stability — no retroactive changes that reprice games already shipped
- [ ] **[nice-to-have]** The project's governance and funding are transparent — a foundation, published finances, or a public roadmap I can plan against

## Openness

- [ ] **[must-have]** Export all of my data in open formats and leave
- [ ] **[must-have]** Self-host the core product
- [ ] **[should-have]** Do everything through the API that I can do in the UI
- [ ] **[should-have]** Read the product's source under an open license

## Platform export

- [ ] **[must-have]** One project exports to desktop, mobile, and (directly or via partners) consoles
- [ ] **[should-have]** My game runs in the browser with a reasonable payload — WebGL today, and a credible WebGPU story
- [ ] **[should-have]** The engine installs from a package registry into my existing toolchain — a library I import, bundle, and tree-shake like any dependency

## Privacy posture

- [ ] **[must-have]** Prevent my data from being used to train AI models
- [ ] **[should-have]** Choose where my data is stored (region/residency)
- [ ] **[should-have]** Control data retention and deletion
- [ ] **[should-have]** Opt out of telemetry and usage tracking

## Scripting

- [ ] **[must-have]** The primary scripting language is productive and fully exposes the engine API, with a debugger behind it
- [ ] **[should-have]** The edit-run loop is fast — hot reload or near-instant preview after a script change
- [ ] **[should-have]** Build gameplay logic with visual scripting without writing code

---

Source: https://ultrametric.ai/productarena/arena/game-engines (evidence-graded verdicts for 8 products) · methodology: https://ultrametric.ai/productarena/methodology

Chips show the top 5 ranked products' current verdict on each requirement — ✓ full · ~ partial · ! disputed · — none · n/a not applicable.

Agenticness — how well agents can access and operate the productAgenticness· 17 items

How well agents can access and operate the product

Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows· 4 items

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 interface

    Core requirement — weighs 3× in arena scoring · 3 of 8 products fully deliver this today

    must-have
  • ai-native userLLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seen

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • ai-native userAn official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assets

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • game developerRun ML models inside the game — an official inference runtime for on-device model execution

    Differentiator, not a dealbreaker — weighs 1× in arena scoring · no product fully delivers this yet

    nice-to-have

Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline· 3 items

Getting content in — automated import, formats, marketplaces

  • technical artistStandard interchange formats — glTF, FBX, USD — import cleanly

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • technical artistAsset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each one

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • game developerA large asset store or package ecosystem gives me ready-made models, tools, and plugins

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 8 products fully deliver this today

    should-have

Automation depth — how much of the product can run unattendedAutomation depth· 4 items

How much of the product can run unattended

Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine· 4 items

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-processing

    Core requirement — weighs 3× in arena scoring · no product fully delivers this yet

    must-have
  • game developer2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthought

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 8 products fully deliver this today

    should-have
  • game developerProfile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavy

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have
  • game developerBuilt-in physics — rigid bodies, collisions, raycasts — works out of the box

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling· 3 items

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 levels

    Core requirement — weighs 3× in arena scoring · 3 of 8 products fully deliver this today

    must-have
  • game developerExtend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically

    Core requirement — weighs 3× in arena scoring · 4 of 8 products fully deliver this today

    must-have
  • studio leadThe project format and tooling play well with version control and multi-person teams — mergeable scenes, diffable text formats, or built-in collaboration

    Important, not disqualifying — weighs 2× in arena scoring · no product fully delivers this yet

    should-have

Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automation· 3 items

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 editor

    Core requirement — weighs 3× in arena scoring · 3 of 8 products fully deliver this today

    must-have
  • game developerGame logic runs headless on servers — a dedicated-server or server-runtime build without rendering

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 8 products fully deliver this today

    should-have
  • game developerTests run headlessly — unit and integration tests of game code execute in CI against the real engine

    Important, not disqualifying — weighs 2× in arena scoring · 1 of 8 products fully deliver this today

    should-have

Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness· 4 items

The terms you build on — licenses, royalties, source access, pricing stability

Openness — open source, data portability, and self-hosting storiesOpenness· 4 items

Open source, data portability, and self-hosting stories

Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export· 3 items

Shipping everywhere — desktop, mobile, console, browser payloads

  • studio leadOne project exports to desktop, mobile, and (directly or via partners) consoles

    Core requirement — weighs 3× in arena scoring · 2 of 8 products fully deliver this today

    must-have
  • web developerMy game runs in the browser with a reasonable payload — WebGL today, and a credible WebGPU story

    Important, not disqualifying — weighs 2× in arena scoring · 2 of 8 products fully deliver this today

    should-have
  • web developerThe engine installs from a package registry into my existing toolchain — a library I import, bundle, and tree-shake like any dependency

    Important, not disqualifying — weighs 2× in arena scoring · 4 of 8 products fully deliver this today

    should-have

Privacy posture — data-handling and privacy storiesPrivacy posture· 4 items

Data-handling and privacy stories

Scripting — writing the game — languages, visual scripting, iteration speedScripting· 3 items

Writing the game — languages, visual scripting, iteration speed

Full evidence behind every verdict lives on the arena page and each product page — chips above deep-link straight to the judged story.