Is Iron Pact free to play?

Iron Pact is currently in Closed Beta. Wishlist on Steam (App ID 3456700) and join the Discord community for beta access. Final monetization model will be announced ahead of open release.

How do I get into the Closed Beta?

Wishlist Iron Pact on Steam and join the official Discord (discord.gg/MUUxP2Uthg). Beta keys are distributed in waves announced on Discord.

Does Iron Pact reset its world?

No. Iron Pact is a single persistent Earth shared by every player. There are no rounds, no seasons, and no resets. Captured territory stays captured; lost territory stays lost.

What are the system requirements?

Iron Pact runs in a modern web browser (Chrome, Firefox, Edge, Safari) with WebGL2 support. There is no install. A desktop or laptop with a discrete GPU is recommended for large engagements.

What is the time commitment? Do I have to play 24 hours a day?

No. Iron Pact ships with a visual automation graph editor that lets you script production, supply, and reactive military behavior so your empire keeps running while you sleep. Players also rely on alliances to cover off-hours.

How does diplomacy work?

Diplomacy in Iron Pact is governed by six server-enforced states: Allied, Non-Aggression Pact (NAP), Ceasefire, Neutral, War, and Grace. Each state controls whether two parties can attack, capture territory from, or observe each other.

Do I need to write code to use the automation system?

No. The automation editor is fully graphical. You drag triggers, conditions, and actions onto a canvas and wire them together. There are no formulas, no scripting language, and no text expressions to author.

Where are the servers and what is the latency?

Iron Pact uses a globally distributed real-time server architecture so a single shared Earth can host players from every region simultaneously. Latency targets sub-150 ms for command actions in supported regions.

Command. Conquer. Dominate the Globe.

One shared Earth. Real-time fronts that don't pause when you log off — forge alliances, hold supply lines, and live with every mile of ground you take or lose.

Wishlist on Steam · Join our Discord

Closed Beta — Wishlist on Steam to stay updated.

Fast Facts

Genre: Persistent real-time strategy MMO (browser-based)
World: Single shared Earth, no resets, no rounds, no seasons
Combat: Real-time, real-distance (km/h, no tiles or hexes)
Diplomacy: 6 server-enforced states — Allied, NAP, Ceasefire, Neutral, War, Grace
Automation: Visual drag-and-drop node graph; no formulas, no code
Platforms: Web browser (Chrome / Firefox / Edge / Safari with WebGL2)
Status: Closed Beta 2026 — wishlist on Steam (App ID 3456700)

A war on every front

Warfare

Move armies in real time across real distance. Cut their supply, dig in on high ground, hit them where their reserves can't reach. Every fight is fought once.

Distance is measured in kilometres, not tiles. A column of armour 47 km out at 60 km/h arrives in 47 minutes — the same 47 minutes that pass on the clock on your wrist. There are no hexes to hide behind, no battle phases, no rolled dice. Engagements resolve continuously on a single persistent shared world, so the army you flanked at dawn is the army your alliance has to live with at noon. Cut a supply line and the front it fed goes quiet within minutes. The map remembers every kilometre your tracks carved into it.

Alliances

Forge pacts or betray allies. Six diplomatic states — Allied, NAP, Ceasefire, Neutral, War, Grace — and every one of them changes who can shoot whom. Treaties have teeth.

Every relation between two parties is governed by exactly one of those six server-enforced states, and the server — not your conscience — decides whether your artillery is allowed to fire. Allied and NAP block attacks and territory capture outright. Ceasefire warns before cancelling. Neutral allows fire but blocks capture. War unlocks both. Grace is a cooldown nobody can skip. Break a pact and the consequences ripple through the alliance marketplace, where graphs you publish tonight will run somebody else's war tomorrow.

Logistics

Armies march on supply lines. Cut them and the front goes quiet. Build them and you outlast everyone — even the alliance you trusted last week.

Production, refining, transport, and forward depots all run as live nodes on the same persistent globe — no abstraction, no off-screen accounting. Sever a single rail spur 200 km behind the line and the divisions it fed run dry within the hour. Reroute around the cut with a graph you wired last week and the front holds. Logistics is not a minigame; it is the war. Players who treat the supply network as seriously as the firing line are the ones whose territory is still on the map a month later.

Persistence

You'll log off at midnight. The enemy in Asia will log on at dawn. The map at noon won't be the map you left.

There are no rounds, no resets, no seasonal wipes. The Earth in Iron Pact is one shared persistent world for every player in every region, and the clock that runs it is the same clock that runs the day outside your window. Ground you take at 23:00 is ground your alliance still holds at 11:00 — unless someone took it back while you slept. Captures are permanent. Losses are permanent. The map at the end of the year is the map every decision in it built, and nobody, not even the developers, can roll it back.

Automate your empire

Wire your war so it keeps fighting while you're at work. Drag-and-drop nodes — no formulas, no code.

Visual node canvas

Drag triggers, conditions, and actions onto the canvas. Build the strategy you can't keep in your head — without writing a single line of code.

The graph editor is fully graphical: every node is a labelled box with named input and output ports, every condition is a structured dropdown plus a typed value, and every choice is bounded to a predetermined set. There are no formulas to type, no scripting language to learn, no text expressions hidden in an "advanced mode". The canvas of connected nodes is the programming surface; nothing else exists. A new player can wire reactive military behaviour, supply chains, and production queues on day one and have them run forever.

Reacts to the war

When the enemy crosses your border, your reserves move. When stockpiles run low, your refineries spin up. When a treaty breaks, every officer in your alliance knows in seconds.

Graphs are event-driven, not polled — they react the same tick a unit enters attack range, the same tick a supply line is severed, the same tick a diplomatic state flips from NAP to War. There is no scheduler ticking past your nodes hoping to catch the change; the engine wakes the exact graphs that listen for the event that just happened. That is why a graph you wrote last week can credibly stand a watch the human player at the keyboard cannot.

Earned, not given

Early war is chaos you control by hand. As your tech tree grows you unlock deeper graphs — logistics, military, relays, comms — and choreograph what used to need a second monitor.

Automation is gated behind the science-pack research tree the same way every other tier-locked capability is. You start with a handful of player-palette nodes covering basic production and reactive movement. Higher tiers unlock conditional branching, relay propagation across alliance members, multi-stage supply scheduling, and finer-grained reactive military behaviour. Nothing in the palette is locked behind a paywall; it is all earned by the labs you fed with the supply lines you built.

Marketplace

Publish your graphs. Steal what your alliance already built. The strategies you write tonight will run wars you'll never see.

The alliance marketplace is the social layer on top of the graph editor. Players publish reusable graphs — defensive standing-orders for a frontier sector, automated science-pack pipelines, supply-line rerouting playbooks, reactive escort behaviour — and other members of the alliance import them with a click. Authorship survives the import. The best graph designers become known by name across the world, and the alliances that recruit them outlast the alliances that don't.

A globe that never resets

Real distance. Real time. Permanent consequences. The war you fight tonight is the war you'll inherit tomorrow.

Real distance, real time

Their armor is 47 km out at 60 km/h. They arrive in 47 minutes. No tiles to count, no hexes to hide in — the map is the world, and the clock is the same one on your wrist.

The simulation runs in real geographic units. Position is longitude and latitude. Movement is kilometres per hour. Distance to contact is the literal great-circle distance between two armies. A unit at 60 km/h covers 60 km in 60 minutes — there is no scaling factor, no game-hour, no tick-speed multiplier. Forward observers, reconnaissance flights, and pre-emptive interdiction all matter because the engagement window is the actual interval between detection and arrival, and the actual interval is enough time to do something about it.

Hold by being there

Roll armor into enemy territory and it's yours. Pull back and you lose it. There's no flag to plant, no siege bar to fill — you either stand on the ground or you don't.

Sector control is implicit on entry. The server resolves ownership by point-in-polygon against the actual land mesh — there is no adjacency graph, no neighbour table, no capture meter. If your unit is standing inside a sector and the diplomatic state with the current owner is War, the sector is yours; if you withdraw and a rival enters, it is theirs. Ocean is no sector at all. The map shows what the world actually is, not an abstract board on top of it.

The war while you sleep

You log off at midnight. The enemy in Asia logs on at dawn. The map at noon won't be the map you left — your alliance Discord will tell you the rest.

Iron Pact is a single persistent shared Earth, which means every timezone is somebody's prime time. Coverage is solved by alliance, not by stamina. A serious alliance staffs the watches it cannot personally stand: graphs on the front, players in the rear, officers in chat, and diplomats already negotiating the next pact. The off-hours you can no longer defend personally are the off-hours your alliance and your automation graphs were built for. That is the whole social contract of the game.

No take-backs

The ground you lose stays lost. The ground you take stays held. No reset, no rounds, no second campaign. The map remembers every mile.

Persistence is the design — not a feature flag, not a server setting, not a season modifier. There is no round timer counting down, no end-of-match scoring screen, no global reset that pretends nothing happened. Every capture, every defeat, every alliance, every betrayal is part of the only Earth the game has. A territory lost on day one of your campaign is still lost on day three hundred, unless you took it back. That is what "persistent" means here, and that is why every kilometre is worth fighting over.

Your path to power

01 · Deploy Pick a corner of the globe. Drop your HQ. Start building before someone else picks the same corner.
02 · Expand Train armies. Take ground. Run supply where the enemy can't see it. Research tech that lets your alliance do what nobody else can yet.
03 · Dominate Stack alliances. Break them when you have to. Hold every sector you can — and remember, when you log off, the war doesn't.