# Riftbound Deploy Explained: The Leaked Radiance Mechanic

_2026-09-08 · RiftCompare_

What Riftbound's leaked Deploy keyword reportedly does, how it's meant to work, and why Riot hasn't confirmed it yet — everything currently known about Radiance's Gear mechanic.

## The short version

- **Deploy is a leaked Gear keyword from Riftbound: Radiance**, reportedly tied to holding one specific battlefield rather than being attached to a unit.
- **Lose the battlefield, lose the card**: the leaked wording says an opponent taking that battlefield kills the Gear outright, not just switches it off.
- **It's the opposite risk profile from [Equip](/keywords/equip)**, which stays functional on its unit regardless of what's happening on the board.
- **Not officially confirmed.** This is sourced to a photo of Riot's own PAX West demo material, not a Riot announcement — see the **[full leak roundup](/blog/riftbound-radiance-leaked-mechanics)** for the source.

**Deploy is one of three new mechanics reportedly leaked from Riftbound: Radiance** ahead of the set's **[23 October 2026 release](/blog/riftbound-radiance-what-we-know)** — photographed on a physical rules-reference card at Riot's own PAX West demo table and shared publicly by Riftbound content creator AskJoshy. It has **not** been confirmed by Riot. Here's exactly what leaked, how the mechanic reportedly works, and what would need to happen before we'd treat any of it as settled.

> "Play this gear only to a battlefield and it will grant benefits while there. When an opponent holds that battlefield, kill this gear."

## How Deploy reportedly works

1. **Play the Gear to a battlefield**, not to your base or a unit — Deploy appears to be a location-bound Gear keyword rather than a unit attachment.
2. **It grants a benefit while you hold that battlefield.** The leaked text doesn't specify what kind of benefit — a stat boost, an ongoing effect, or something else entirely could all fit "grant benefits."
3. **Lose the battlefield, lose the card.** If an opponent takes control of the battlefield the Gear is deployed to, the card is killed outright — not just deactivated.

That third step is the part worth sitting with. Most of Riftbound's existing Gear interacts with a unit via **[Equip](/keywords/equip)**, which stays attached and functional regardless of what's happening on the board around it. Deploy, as leaked, ties the card's *survival* to board state — a meaningfully riskier trade for whatever benefit it grants.

## What kind of benefit might Deploy actually grant?

The leaked wording — "it will grant benefits while there" — is left deliberately vague, and it's worth being honest about how little that actually tells us. Riftbound's existing Gear generally does one of a few things once attached: raise a stat, grant a keyword the unit wouldn't otherwise have, or provide a one-time or repeatable triggered effect. Nothing in the Deploy leak rules any of those out, and nothing points specifically toward one over the others either. What the wording does confirm is that whatever the benefit is, it's tied to the *location* rather than to a unit standing on it — a structural detail, not a power-level one. Until an actual Deploy card surfaces with real stats and real wording, "some kind of ongoing bonus, size and shape unknown" is the most honest read available.

## A hypothetical turn, to make the risk concrete

Picture a simplified sequence, purely to illustrate the mechanic rather than to describe any real card: you play a Deploy Gear to a battlefield you currently control, and for as long as you hold it, the Gear does something useful. Your opponent then commits units to contest that same battlefield — under Riftbound's existing rules, battlefields change hands through combat, the same fight **[Hunt](/keywords/hunt)** already rewards winning. If your opponent takes the battlefield, the Deploy Gear doesn't just go quiet; per the leaked wording it's killed outright, and you're down a whole card with nothing to show for it. That's the entire risk profile in one sequence: Deploy asks you to defend a piece of ground you've already invested a card into, with a real card-disadvantage penalty if you can't hold it.

## Deploy vs Equip: gear tied to a place, not a unit

**[Equip](/keywords/equip)** attaches a Gear card to a *unit* you control, and it stays there — the card cares about the unit, not the battlefield the unit happens to be standing on. Deploy, as leaked, reverses that: the Gear cares about the *battlefield*, not any specific unit, and it's vulnerable to something Equip never has to worry about — losing that one location. If the leak holds up, Deploy and Equip will likely coexist as two different flavours of "gear investment" rather than one replacing the other: Equip for a stable, unit-bound bonus, Deploy for a higher-risk, higher-reward battlefield commitment.

## How Deploy interacts with Riftbound's three-battlefield structure

A Riftbound game is played across **[three Battlefields](/guides/how-a-riftbound-deck-is-built)**, and control of each one shifts over the course of a match rather than being settled once at the start. That structure changes what "commit a Deploy Gear to a battlefield" actually means in practice: you're not choosing a location in a vacuum, you're choosing which of three ongoing fights to stake a whole card's worth of risk on. A battlefield you're already winning is a much safer target for a Deploy Gear than one that's actively contested, since the risk of losing the card outright tracks directly with how likely you are to lose that specific fight. If the leak holds up, reading the board's three battlefields correctly before committing a Deploy Gear will likely matter as much as anything printed on the card itself.

## Building around Deploy, if the leak holds up

Riftbound already has two keywords built around battlefield control that a Deploy card would naturally want to pair with:

- **[Hunt](/keywords/hunt)** grants XP for conquering or holding a battlefield — exactly the state a Deploy card needs to survive, so a Hunt unit defending the same battlefield as a Deploy Gear turns one board position into two payoffs at once.
- **[Ganking](/keywords/ganking)** lets a unit move directly from one battlefield to another — useful for reinforcing a battlefield that's about to fall out of your control before the Deploy Gear on it gets killed.

None of this is a confirmed archetype — it's a reasonable read of how Deploy would interact with mechanics that already exist, clearly labelled as such. That defensive angle likely matters more for Deploy than it does for a typical Gear card, precisely because Deploy's downside — losing the whole card outright — is so much steeper than an ordinary Gear's downside of simply sitting unused for a turn. A deck built around Deploy will probably want to treat "defend this specific battlefield" as a real strategic priority, closer to how a control deck protects a key removal spell than how an aggro deck plays out a stat stick and moves on. None of that changes if Deploy's actual benefit turns out to be small — a modest bonus tied to a battlefield you can't reliably hold is still a worse trade than the same bonus attached to a unit that survives regardless of who's winning the board. It also means Deploy is unlikely to be a card you play reflexively the moment it's drawn; reading the board first, then deciding whether any battlefield is safe enough to justify the risk, is closer to how the leaked wording suggests this card wants to be played.

## Why a single keyword leaks before a full spoiler season

Full-set spoiler seasons — every card in a set revealed on a schedule — are how Riftbound has confirmed mechanics for each of its previous releases. A leak like this one sits ahead of that process entirely: it's a photograph of internal-facing reference material rather than a scheduled reveal, which is why real, quotable wording can surface months before a set goes through its own proper preview cycle. That gap between "photographed once at a convention" and "spoiled on schedule with card art and Core Rules-verified wording" is exactly the gap this page is being careful to flag throughout.

## What would actually confirm Deploy

Three things would move Deploy from "leaked" to "confirmed" in our own coverage: an official Riot channel — a dev blog, a verified social post, or a proper spoiler-season card reveal — showing the keyword; a physical or digital card image with Deploy printed on it in final form; or wording that can be checked against an updated Core Rules PDF, the same bar **[Empower](/keywords/empower)**, **[Flow](/keywords/flow)** and **[Burn](/keywords/burn)** eventually cleared for Vendetta. Any one of those would be enough. A second demo-table photo, even from a different convention, would not — it would still be the same category of unofficial sighting this article is already treating carefully.

## How Deploy compares to Showoff and Disarm

Deploy is one of three mechanics in the same leak. **[Showoff](/guides/riftbound-showoff-explained)** is a modal reveal effect triggered as you play a card; **[Disarm](/guides/riftbound-disarm-explained)** weakens an enemy unit's Might when the Disarm unit attacks. Unlike Deploy's battlefield-control angle, neither of the other two cares about board position at all, which is part of why the three don't appear designed to combo directly with each other the way Vendetta's Empower, Flow and Burn were — see the **[full leak roundup](/blog/riftbound-radiance-leaked-mechanics)** for the source photo and all three side by side.

## Is Deploy officially confirmed?

No. This is reported from a fan photo of Riot's own physical demo reference material at PAX West, not a Riot announcement. We'll only add Deploy to our verified keyword glossary — the way **[Empower](/keywords/empower)**, **[Flow](/keywords/flow)** and **[Burn](/keywords/burn)** were added for Vendetta — once its wording can be checked against Riot's own Core Rules PDF or an official card image. Until then, treat everything on this page as **reported, not settled**. There's also nothing to buy yet: no confirmed Deploy card exists, so the only thing actually trackable today is **[Radiance's sealed pre-order pricing](/radiance-preorders)**, which the **[full leak roundup](/blog/riftbound-radiance-leaked-mechanics)** links out to and which we'll keep updating independently of whatever any individual card in the set turns out to do.

## FAQ

**What is Deploy in Riftbound?**

As leaked from a Riot demo at PAX West: "Play this gear only to a battlefield and it will grant benefits while there. When an opponent holds that battlefield, kill this gear." It's reportedly a Gear keyword tied to controlling one specific battlefield, not yet confirmed by Riot.

**How does the Deploy mechanic work?**

As leaked: you play the Gear to a battlefield rather than to a unit or your base. While you hold that battlefield, it grants a benefit (the leak doesn't say what kind). If an opponent takes the battlefield, the Gear is killed outright.

**What happens if I lose the battlefield a Deploy gear is on?**

Per the leaked wording, the Gear is killed — not deactivated or returned to hand, but removed from the game the way any killed permanent would be.

**How is Deploy different from Equip?**

Equip attaches a Gear card to a unit, and it stays functional regardless of board state. Deploy, as leaked, attaches to a battlefield instead of a unit, and is destroyed if you lose control of that battlefield — a much higher-risk trade for whatever benefit it grants.

**Is Deploy confirmed by Riot?**

No. This is reported from a fan photo of Riot's own physical demo reference material at PAX West 2026, not an official Riot announcement or Core Rules update.

**How is Deploy different from Showoff and Disarm?**

Deploy is a Gear keyword about holding a battlefield; Showoff is a modal reveal effect triggered on play; Disarm weakens an enemy unit's Might on attack. All three reportedly leaked together but don't appear designed to combo directly, unlike Vendetta's Empower/Flow/Burn.

Source: https://riftcompare.com/guides/riftbound-deploy-explained