Horde integration is available on the Studio and Enterprise plans. Please contact us in order to receive a copy of the Diversion Horde installation files.
Prerequisites
- Admin access to your Horde Server and Horde Agent machines (Windows).
- Access to UE source on GitHub via your Epic↔GitHub linked accounts. This is a general Horde requirement, as Horde build steps require access to the engine source and tools such as UAT & UBT.
1) Install & sign in to Diversion (Server + Agents)
- Run the Diversion for Windows installer on the Horde Server and on every Horde Agent.
- Launch Diversion and sign in on both Server and Agents so the integration has proper access to the UE5 source repository.
2) Prepare a UE5 source repo in Diversion (Windows)
2.1 Import the UE source into Diversion
Preparing a UE5 source repository in Diversion is handled by a dedicated import tool, currently in closed preview. It clones your UE fork, runs Epic’sSetup.bat, and commits the engine tree into a Diversion repository for you.
The import tool is not yet publicly available. Contact
support@diversion.dev for the tool and the
accompanying setup instructions.
2.2 Add your UE project to this source tree
Place your game project (that should compile against this source engine) in the expected path (often the UE repo root or a sibling path your BuildGraph expects). Commit required files to Diversion.3) Point your Horde stream at a Diversion repo/branch
Do this after your UE5 source repository is prepared (Section 2). Edit your stream config (*.stream.json) under the Horde config directory:
C:\\ProgramData\\Epic\\Horde\\Server\\
name field targets your Diversion repo and branch:
If your configs are split (globals → project → stream), place name in the stream JSON that represents your UE source stream.
4) Configure Horde for your UE source stream
- Confirm your Horde config files live under
C:\\ProgramData\\Epic\\Horde\\Server\\. - Ensure your project (
*.project.json) references your stream (*.stream.json). - In the stream JSON, set the Diversion repo and branch mapping (see Section 3), then define the proper job templates (BuildGraph) and other general Horde requirements.
- Start with a minimal Editor‑only BuildGraph job to validate the pipeline was set correctly.
Horde’s config stack is Globals → Projects → Streams. Using the.project.json/.stream.jsonextensions enables JSON‑schema tooling.
5) Smoke test
- Restart or hot‑reload Horde after saving configs.
- In Horde Dashboard, open your project/stream, queue a small BuildGraph job based on your existing configuration, and confirm agents sync from Diversion and build.
Quick reference (Windows)
-
UE setup
Further reading
- UE on GitHub — linking Epic↔GitHub accounts
- Download UE Source — official guide
- Build UE from Source — Windows notes
- Horde (Overview) — overview documentation
- Horde Orientation — schema server, configs
- Horde Build Automation (Overview) — build automation overview
- Horde Build Automation (Tutorial) — build automation tutorial

