Skip to content
Automation Forge

Download

Windows 10 / 11 · 64-bit

Unreal Engine 5.8

Free on your own hardware. Open where it counts.

One installer. Every set.

The hub installs any set into Unreal Engine 5.8 with its dependencies in one click, and tells you when something newer exists. Sign in once; free plugins are added to your account with a click.

Latest release

Download for WindowsSee what it installsYour account

Every plugin is added to your account first. Free ones with one click; paid ones bought once.

The installer needs no administrator rights. The hub asks for them once, only when it writes into an engine under Program Files. Windows may ask you to confirm the first run of software from a new publisher.

The Automation Forge hub: the sets down the left, the selected set’s plugins on the right, one Install button per plugin
The hub on a workstation with Unreal Engine 5.8 — every set, what each plugin is, and one action per plugin.

How it goes

Eight steps, the last of which repeats.

The whole setup in under eight minutes: the hub installed and signed in, the AutomationForge set and then MotionForge and MeshForge installed, the checkout for a paid plugin, updates read and applied — the hub’s own included — and the plugins turned on in a fresh Unreal Engine 5.8 project.

01

Install the hub

One installer, no administrator prompt. It finds every Unreal Engine on the machine by itself.

02

Sign in once

The hub opens the account site for a moment and connects that computer to your account. Everything the account holds installs from then on; nothing installs without it.

03

Pick an engine, or a project

Sets install into Engine/Plugins/AutomationForge — or into a project’s own Plugins folder, if you would rather keep them with the game.

04

Install a set

A set is a core, its providers, its add-ons and its toolsets, dependencies first. Install on a free plugin adds it to your account and installs it in one go; a paid one is bought once on the account site. The editor’s Plugins window lists them like any other plugin.

05

Turn them on in a project

Installed into an engine, a plugin is available to every project and on in none of them, so each project takes only what it uses. The hub’s own menu in the editor lists what is installed and turns on what this project needs — the same edit the Plugins window makes — and the editor loads it after a restart.

06

Enter a key once

A Runpod key or a Hugging Face token is an account you have, not something a plugin owns — so the hub keeps them in one place, in the operating system’s credential vault, shared by every set that needs them. It also says what a key alone does not buy: some models need their terms accepted or access requested, and a token without that grant installs perfectly and fails later.

07

Start a runner

Some providers run a model on your own machine in a container, or on a GPU rented by the hour. The hub starts and stops them, says whether one is answering and what a rented one is costing right now — so nothing bills overnight because a window was closed.

08

Stay current

The hub watches from the tray and says when a newer release exists — for the plugins and for itself — with the notes for every version since the one you have. Nothing installs without you.

Prefer a terminal

The same core, as a command.

forge is the hub without the window: the installer, the updater and the channel switch, for scripts, CI and the agents working beside you. The hub itself runs it when an engine needs administrator rights, so both surfaces install exactly the same bytes and keep the same receipts.

forge engines                  the Unreal installations on this machine
forge login                    once; the browser says yes
forge install motionforge      a set, dependencies first — added to your account as it goes
forge install FaceForge --project C:\Games\MyGame
forge enable MotionForge --project C:\Games\MyGame
forge update                  everything on a target to its latest
forge channel nightly          follow the nightly builds

Also