Cyberpunk RED Guide Hub | Netrunning Guide | NET Architecture Guide | Cyberware Guide | Cyberpunk RED Guides
The Short Answer
Cyberpunk RED programs are not a list to complete. They are limited deck slots that decide what kind of problem the Netrunner can solve while the crew holds the physical job together. Start with the work your campaign actually gives the crew, then choose a small mix of progress, protection, and response tools that supports it.
Programs and hardware share the same Cyberdeck space. That makes deck building a practical trade: one more answer to an expected NET problem means one less slot for a different answer. A focused deck becomes memorable because the player knows what it is for before the access point is found.
Get the Free GM Session Kit
Session Zero template, recap format, and a pricing cheat sheet - everything you need to run a better table and, if you want, get paid for it.
No spam, unsubscribe anytime.
Hot Take
The first program decision should be "What do I want the crew to dare?" not "What gives me the biggest number?"
A tool that helps the team reach a file, keep an exit open, survive a known threat, or leave evidence behind can change the whole job. A deck filled only with answers to private NET combat invites the Netrunner to solve a problem that no one else can see. Make the loadout create openings the rest of the table can use.
Three Program Jobs
The Core Rulebook organizes non-Black ICE programs into three broad jobs. This is the best first filter when deciding what belongs in a deck.
| Program type | Table purpose | Deck-building question |
|---|---|---|
| Booster | Improves a relevant part of the Netrunner's work while it is active. | Which recurring task must succeed for this crew's usual jobs? |
| Defender | Stops or reduces specific threats while it is active. | What danger is common enough to reserve a slot for protection? |
| Attacker | Damages or disables an eligible program or Netrunner, then deactivates after use. | What target is worth spending a response on when pressure rises? |
The labels explain function, not a mandatory recipe. An investigation-heavy campaign may value tools that support getting in, learning what is ahead, and leaving without a trace. A campaign with hostile Netrunners or repeated digital defenses may make a different mix worthwhile. Let the regular job pattern, not anxiety about every imaginable encounter, decide the loadout.
Programs Have A Tempo
Programs are active tools inside the Architecture, not passive character-sheet bonuses. The Core Rulebook makes activation and deactivation NET Actions, limits each loaded program's activation in a Meatspace Round, and treats Attackers differently because they deactivate after their attack. Those rules create a useful tempo:
- Read the immediate threat and the crew's physical objective.
- Activate the tool that changes the next decision.
- Use its advantage before the scene moves on.
- Decide whether the program is still worth keeping active or whether its slot and actions must serve a new problem.
This is why a deck cannot be evaluated only by its printed effect. A useful program needs the right target, a safe moment to activate it, and enough crew support for the Netrunner to turn its effect into progress. A strong floor plan and a focused deck reinforce one another.
REZ, Derezzing, And Replacement Pressure
Programs can take damage while they are running. The Core Rulebook uses REZ as a program's durability, and a program reduced to zero REZ is Derezzed rather than automatically removed from the Cyberdeck. The Netrunner can restore a Derezzed program's working state through the appropriate NET Actions. A destroyed program is a different problem: it must be replaced.
That distinction creates good aftermath decisions. If the crew has a safe exit, the Netrunner may accept temporary damage and reset later. If the job is still escalating, protecting a key active program can matter as much as protecting the Netrunner. Treat a destroyed tool as a story cost as well as a purchase: who can supply the replacement, what does the crew give up to acquire it, and why did that program matter to the character?
Start With A Job, Then Fill Slots
Avoid treating a cyberdeck as a shopping list. Use a short planning pass instead:
- Name the job pattern: infiltration, investigation, hostile site work, recurring defense, or something specific to the campaign.
- Choose one Booster that supports the action the Netrunner expects to take most often.
- Choose one Defender only if it answers a threat the table truly sees.
- Add an Attacker when the crew's jobs reasonably create an eligible target worth confronting.
- Leave room for hardware only when it supports the same job pattern rather than a hypothetical future build.
- After each run, replace a slot only when the session showed a real gap.
This approach also makes upgrades easier to judge. Black Chrome adds options that can expand the practical capacity of certain integrated or worn setups, but an extra slot is only useful when it serves a real recurring decision. The Cyberware Guide can help when the deck setup depends on Neural Link, Interface Plugs, Cyberarm integration, or other prerequisites.
Do Not Confuse Programs With Black ICE
Programs are the Netrunner's normal toolkit. Black ICE is a separate category with its own behavior, larger deck footprint when a Netrunner runs it, and more dangerous encounter consequences. A Demon is different again: it is an intelligent Black ICE system that operates Control Nodes to defend a physical space.
That distinction matters in play. A Booster, Defender, or Attacker is a deliberate tool choice for the Netrunner. Black ICE changes the shape of NET conflict. A Demon turns the surrounding location into part of the fight. Read the NET Architecture Guide when you need the job-site side of Control Nodes, floors, Black ICE, and Demons.
Make The Deck Visible To The Crew
The Netrunner does not need to recite every active effect. Tell the group the concrete change the selected program enables:
| Instead of saying | Say | What the crew learns |
|---|---|---|
| "I activate a Booster." | "I can find the route through this system faster." | The team needs to create time or move when the route appears. |
| "I use a Defender." | "I can absorb this digital pressure for a moment." | The crew has a short window to finish its physical objective. |
| "I fire an Attacker." | "I can disable the program blocking the door controls." | The group can decide whether opening that path is worth the attention. |
This keeps the rules accurate without turning the turn into a private report. The program matters because it changes the shared operation, not because it has an impressive name on the deck.
Where To Go Next
Use the Netrunning Guide for the complete job-site procedure and the NET Architecture Guide to build a physical location worth hacking. Return to the Cyberpunk RED Guide Hub or guide directory for every live guide.
A dedicated Cyberdeck guide is planned. Until it is live, use the Core Rulebook for exact deck capacities, program lists, hardware options, installation details, program statistics, and Black ICE rules. Use Black Chrome for its exact additional equipment options and prerequisites.
Sources And Scope
This guide summarizes Cyberdeck program use, Boosters, Defenders, Attackers, activation, REZ, Derezzing, Black ICE distinctions, and program-hardware slot tradeoffs from the Cyberpunk RED Core Rulebook. It also notes that Black Chrome includes additional relevant Cyberdeck-capacity options. It does not reproduce program tables, program statistics, prices, exact effects, hardware tables, deck capacities, or Black ICE statistics. Use those books for exact rules and values.
