Swarming
Рой
Offense Takes Depth —
mass attack by individually weak agents
Moats it grows into
This takes; it does not hold. Mass overwhelms a defender for a moment, but a swarm is an event, not a moat — it disperses, the defender adapts, and the coordination gets no deeper as a defence with your scale. It is an assault, a tactic, not a structure a rival must overcome. A moat can grow out of the swarm only if the units become a lasting network — network effects or a community that stays after the rush — and that is a different build; the swarming itself holds nothing.
Summary
Swarming wins by numbers — many individually weak, cheap units attack at once and overwhelm a defender built for a few strong ones. Coordination and mass do the work, not any single agent. It can take ground a stronger opponent holds, but keeps nothing: the swarm disperses and the defender adapts. It is an assault, not a defence.
How it works
The mechanism is overwhelming a defence tuned for scale, not for count. A defender who can stop a few large threats is helpless against thousands of tiny ones arriving together — each cheap enough to lose, all coordinated to hit the same point. The cost asymmetry favours the attacker: your units are disposable, and the defender must answer every one.
The weakness is that a swarm is a moment, not a state. Once it disperses, the ground is undefended again, and any competent defender adapts — rate limits, filtering, distributed capacity — so the same swarm fails next time. You spent coordination to win an instant, and unless that instant is used to build something, the position reverts. Numbers win the rush; they do not garrison the ground.
Do you have it
- Your force is many cheap, similar units acting together, not a few strong ones.
- You win by overwhelming a defender's capacity, not by being better unit for unit.
- The advantage lasts only during the coordinated push and fades once it stops.
- The other side can neutralise you by adapting its defences, not by matching your strength.
How to dig it
- Coordinate the many so they hit one point together, since scattered pressure achieves nothing.
- Keep each unit cheap and disposable, so losing them does not cost you the attack.
- Concentrate the swarm on a defence tuned for a few large threats, not many small ones.
- Turn the crowd into a lasting network during the rush, or the win disperses with it.
How it erodes
- The defender adds rate limits or filtering, and the same swarm no longer gets through.
- Coordinating the crowd gets harder as it grows, and the attack loses its timing.
- The units drift away once the rush ends, leaving nothing behind them.
- A defender with distributed capacity simply absorbs the mass without breaking.
Solo, without capital
Swarming can favour a solo builder, because it needs coordination and cheap units rather than capital — one person can mobilise a crowd, a bot fleet or a flood of low-cost content this quarter. What a solo builder cannot do is hold what the swarm takes; the moment it disperses, a resourced defender adapts and the ground reverts. Use the rush to convert the crowd into something that stays — a community, a network — before it scatters.
In nature, in business
- Nature
- bees
- Business
- DDoS, Zerg rush
Cases
- r/wallstreetbets — Thousands of small retail traders coordinated to buy GameStop at once, squeezing hedge funds that had shorted it.
- Anonymous — Coordinated volunteers ran distributed denial-of-service floods, many weak machines together taking a target's site offline.
- Honeybees — Defend the hive by mobbing an intruder together, overwhelming an animal no single bee could harm.