Install
brew install --cask epic-games
vs Unity
vs Godot Engine
vs three.js
vs Babylon.js
vs Bevy
vs PlayCanvas
vs PhaserTry itExperimental
See what an agent can do with Unreal Engine before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$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/licenserecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
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 workflowsevidence →
AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inference
Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipelineevidence →
Getting content in — automated import, formats, marketplaces
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engineevidence →
The engine core — rendering, 2D, physics, performance at scale
Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor toolingevidence →
The editor as a product — scene tools, extensibility, team workflows
Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automationevidence →
The engine without a human — CLI builds, CI test runs, dedicated servers
Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing opennessevidence →
The terms you build on — licenses, royalties, source access, pricing stability
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform exportevidence →
Shipping everywhere — desktop, mobile, console, browser payloads
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Scripting — writing the game — languages, visual scripting, iteration speedScriptingevidence →
Writing the game — languages, visual scripting, iteration speed
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Unreal Engine stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Scoped API keys · MCP server · Machine-readable spec · Versioning policy · API sandbox · Full data export · Game logic runs headless on servers — a dedicated-server or server-runtime build without rendering · Tests run headlessly — unit and integration tests of game code execute in CI against the real engine
Subscribe to events via webhooks
n/an/a
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
—–
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
—0/10
Set up automations that run autonomously in the background
~5/10
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
An agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interface
~6/10
LLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seen
—0/10
An official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assets
—0/10
Run ML models inside the game — an official inference runtime for on-device model execution
—–
Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline
Getting content in — automated import, formats, marketplaces
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Automation depth
Define rules that trigger actions automatically on events
✓6/10
unlocks → Versioned workflows · LLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seen · An official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assets · Run ML models inside the game — an official inference runtime for on-device model execution
Schedule recurring jobs or workflows
—0/10
Perform bulk operations across many items at once
~5/10
Version, review, and roll back my automations
—–
Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine
The engine core — rendering, 2D, physics, performance at scale
2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthought
—–
Profile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavy
—0/10
Built-in physics — rigid bodies, collisions, raycasts — works out of the box
—–
The engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processing
~5/10
Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling
The editor as a product — scene tools, extensibility, team workflows
The project format and tooling play well with version control and multi-person teams — mergeable scenes, diffable text formats, or built-in collaboration
—–
A full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels
✓7/10
Extend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically
✓8/10
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
Build and export the project from the command line, headless, in CI — no human clicking an editor
✓8/10
Game logic runs headless on servers — a dedicated-server or server-runtime build without rendering
—0/10
Tests run headlessly — unit and integration tests of game code execute in CI against the real engine
—–
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
The project's governance and funding are transparent — a foundation, published finances, or a public roadmap I can plan against
—0/10
The license is permissive with no royalties or per-install fees — I keep what my game earns
—0/10
Read and modify the full engine source when I hit a wall
✓7/10
The pricing and license terms have a track record of stability — no retroactive changes that reprice games already shipped
—0/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export
Shipping everywhere — desktop, mobile, console, browser payloads
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Scripting — writing the game — languages, visual scripting, iteration speedScripting
Writing the game — languages, visual scripting, iteration speed
Sorted by importance (agentic first) (high → low) · 56/56 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Build and export the project from the command line, headless, in CI — no human clicking an editor Ci | game developer | Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automation | 3 | full | 8/10 | Tprobed | |
Extend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically Extensibility | game developer | Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling | 3 | full | 8/10 | Xcommunity | |
A full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels Editor | technical artist | Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling | 3 | full | 7/10 | Xcommunity | |
One project exports to desktop, mobile, and (directly or via partners) consoles Targets | studio lead | Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export | 3 | partial | 7/10 | Xcommunity | |
An agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interface Agent editor | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 3 | partial | 6/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | full | 6/10 | Xcommunity | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 6/10 | Tprobed | |
The engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processing Rendering | game developer | Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine | 3 | partial | 5/10 | Xcommunity | |
The primary scripting language is productive and fully exposes the engine API, with a debugger behind it Language | game developer | Scripting — writing the game — languages, visual scripting, iteration speedScripting | 3 | partial | 5/10 | Xcommunity | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
The license is permissive with no royalties or per-install fees — I keep what my game earns License | studio lead | Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Read and modify the full engine source when I hit a wall Source | game developer | Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness | 2 | full | 7/10 | Tprobed | |
Asset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each one Import | technical artist | Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline | 2 | partial | 6/10 | Cclaimed | |
Build gameplay logic with visual scripting without writing code Visual | technical artist | Scripting — writing the game — languages, visual scripting, iteration speedScripting | 2 | disputed | 6/10 | Dcontradicted | |
The edit-run loop is fast — hot reload or near-instant preview after a script change Iteration | game developer | Scripting — writing the game — languages, visual scripting, iteration speedScripting | 2 | partial | 6/10 | Cclaimed | |
A large asset store or package ecosystem gives me ready-made models, tools, and plugins Marketplace | game developer | Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline | 2 | partial | 5/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Tprobed | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | disputed | 3/10 | Dcontradicted | |
An official AI assistant inside the engine helps with engine tasks — generating scripts, answering API questions, scaffolding scenes or assets Copilot | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 2 | none | 0/10 | ||
Game logic runs headless on servers — a dedicated-server or server-runtime build without rendering Server | game developer | Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automation | 2 | none | 0/10 | ||
LLM-generated code mostly works on the first try — stable, well-documented APIs with abundant public examples the models have seen Codegen | ai-native user | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 2 | none | 0/10 | ||
My game runs in the browser with a reasonable payload — WebGL today, and a credible WebGPU story Web | web developer | Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export | 2 | none | 0/10 | ||
Profile and scale — a real profiler, plus data-oriented paths (ECS, jobs, instancing) when scenes get heavy Performance | game developer | Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
The pricing and license terms have a track record of stability — no retroactive changes that reprice games already shipped Trust | studio lead | Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness | 2 | none | 0/10 | ||
2D is a first-class workflow — sprites, tilemaps, 2D physics — not a 3D afterthought 2d | game developer | Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine | 2 | none | untested | none yet | |
Built-in physics — rigid bodies, collisions, raycasts — works out of the box Physics | game developer | Core engine — the engine core — rendering, 2D, physics, performance at scaleCore engine | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Standard interchange formats — glTF, FBX, USD — import cleanly Formats | technical artist | Asset pipeline — getting content in — automated import, formats, marketplacesAsset pipeline | 2 | none | untested | none yet | |
Tests run headlessly — unit and integration tests of game code execute in CI against the real engine Testing | game developer | Headless automation — the engine without a human — CLI builds, CI test runs, dedicated serversHeadless automation | 2 | none | untested | none yet | |
The engine installs from a package registry into my existing toolchain — a library I import, bundle, and tree-shake like any dependency Web | web developer | Platform export — shipping everywhere — desktop, mobile, console, browser payloadsPlatform export | 2 | none | untested | none yet | |
The project format and tooling play well with version control and multi-person teams — mergeable scenes, diffable text formats, or built-in collaboration Collaboration | studio lead | Editor tooling — the editor as a product — scene tools, extensibility, team workflowsEditor tooling | 2 | none | untested | none yet | |
The project's governance and funding are transparent — a foundation, published finances, or a public roadmap I can plan against Governance | studio lead | Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityLicensing openness | 1 | none | 0/10 | ||
Run ML models inside the game — an official inference runtime for on-device model execution Inference | game developer | Ai workflows — AI in the engine loop — agent-driven editors, copilots, codegen-friendly APIs, runtime inferenceAi workflows | 1 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 44 stories with headroom
What would move Unreal Engine’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
No evidence in the pack of any built-in AI assistant inside Unreal Editor that users can delegate tasks to; all documentation covers Blueprints, C++, Python scripting, plugins, and CLI tools, not an AI agent.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Unreal Engine is a platform/tool (not an agent), so the MCP-server axis fairly applies, but evidence shows no official Epic-maintained MCP server exists (GitHub search for `mcp org:EpicGames` returns 0 results) and the most popular community MCP integration is unmaintained since 2025, meaning there's no first-party way to plug MCP servers into Unreal for tool use.
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Unreal Engine is a platform/tool (not itself an agent), so an official MCP server axis applies, but evidence shows no official Epic MCP server exists — a GitHub org search returns 0 results, and the most popular community MCP integration is unmaintained since 2025.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Evidence covers Blueprints, C++, plugins, source-code access, and asset management, but nothing addresses exporting a project's proprietary .uasset/.umap data into open interchange formats to allow a clean migration away from Unreal.
Licensing openness — the terms you build on — licenses, royalties, source access, pricing stabilityThe license is permissive with no royalties or per-install fees — I keep what my game earns
nonemoves PA Scoreimpact 30
Community evidence explicitly documents that Unreal charges a 5% royalty on gross revenue after the first $1M (or $3,000/quarter) — this is the opposite of 'no royalties, keep what you earn.' No evidence pack item supports a royalty-free/no-fee licensing model; instead multiple citations (comm-1, comm-9, comm-13, comm-2) confirm a royalty-based commercial license.
Agenticness — how well agents can access and operate the productPoint an agent at llms.txt or agent-oriented docs
nonemoves agent-readyimpact 30
A direct probe found no llms.txt on Epic's domains, and appending .md to docs URLs returns the HTML SPA shell rather than agent-readable markdown, meaning there is no mechanism to point an agent at machine-readable docs.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
No evidence in the pack of Unreal Engine surfacing AI-generated insights or suggestions from project data; docs cover Blueprints, C++, Python scripting, plugins, and networking but nothing about analytics/AI-driven suggestions, and the probe notes the engine has no official MCP or AI-native tooling exposure.
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
Evidence shows only traditional scripting/programming interfaces (Blueprints, C++, Python, CLI args) with no natural-language command layer; the probe explicitly notes no official Epic MCP server, no llms.txt, and only an unmaintained community MCP project, meaning there's no documented way to operate Unreal via natural-language commands.
Showing the top 8 of 44 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map4 surfaces · 22 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Documentation docs19 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- An agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interface
- Asset import is automatable — import hooks, presets, and pipeline scripts process incoming assets without hand-clicking each one
- A large asset store or package ecosystem gives me ready-made models, tools, and plugins
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- A full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels
- Extend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically
- Build and export the project from the command line, headless, in CI — no human clicking an editor
- Read and modify the full engine source when I hit a wall
- Do everything through the API that I can do in the UI
- One project exports to desktop, mobile, and (directly or via partners) consoles
- The edit-run loop is fast — hot reload or near-instant preview after a script change
- The primary scripting language is productive and fully exposes the engine API, with a debugger behind it
- Build gameplay logic with visual scripting without writing code
GitHub README13 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- An agent can drive the editor and project programmatically — create scenes and nodes, edit properties, trigger builds — through a documented scriptable interface
- A large asset store or package ecosystem gives me ready-made models, tools, and plugins
- Perform bulk operations across many items at once
- Build and export the project from the command line, headless, in CI — no human clicking an editor
- Read and modify the full engine source when I hit a wall
- Do everything through the API that I can do in the UI
- Read the product's source under an open license
- Self-host the core product
Hacker News9 stories
- A large asset store or package ecosystem gives me ready-made models, tools, and plugins
- Define rules that trigger actions automatically on events
- The engine ships a modern production 3D renderer — PBR materials, global illumination or baked lighting, shadows, post-processing
- A full visual editor — viewport, inspector, prefabs/scene composition — is the primary way to build levels
- Extend and automate the editor itself — custom tools, editor scripts, plugins that manipulate scenes and assets programmatically
- Read and modify the full engine source when I hit a wall
- One project exports to desktop, mobile, and (directly or via partners) consoles
- The primary scripting language is productive and fully exposes the engine API, with a debugger behind it
- Build gameplay logic with visual scripting without writing code
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$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/licensereproduced$ 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/license
github raw README: HTTP 404
unrealengine.com license: HTTP 403
Business model
Free under $1M lifetime gross revenue; 5% royalty above $1M attributable to the UE product (Epic Games Store sales royalty-free); seat licenses for non-game commercial use over $1M.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents