Cyberpunk RED Guide Hub | Cyberpunk RED Roles Guide | Cyberpunk RED Guides
The Short Answer
Cyberpunk RED netrunning works best as one part of a physical job, not as a solo mini-game. The Netrunner has to find and stay near a local access point, navigate a NET Architecture's floors, manage programs and Black ICE, and use Control Nodes or files to change what the rest of the crew can do in Meatspace.
That is the practical rhythm: the team gets the Netrunner to the system, protects the route and the access point, and acts on the opening the Netrunner creates. The Netrunner buys the crew a door, camera loop, elevator, alarm delay, data file, or new complication. Everyone gets a reason to make the next decision.
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 worst way to run a Netrunner is to announce a hack, move the other players away from the table, and start a private puzzle. The rules already give you the better version: the Netrunner is in the building, the access point has a physical location, and Control Nodes affect the same space the crew is trying to survive.
Make every Architecture protect a concrete thing. If no one outside the NET cares whether the next floor is breached, it is not a job scene yet. Put a door, camera, drone, elevator, sprinkler, file, or alarm on the line and let the team decide how long the Netrunner gets to work.
What A Netrunner Needs
The Core Rulebook's baseline is straightforward: a Netrunner needs a Neural Link and Interface Plugs to use a Cyberdeck, plus Virtuality Goggles to stay aware of Meatspace while seeing the NET. The Cyberdeck has limited slots shared by programs and hardware, so a deck is a set of tradeoffs rather than a complete toolbox.
| Part of the kit | Why it matters at the table |
|---|---|
| Interface Role Ability | Determines the Netrunner's NET Actions and enables the Role's NET work. |
| Cyberdeck | Holds the programs and hardware that define a run's options. |
| Virtuality Goggles | Let the Netrunner perceive NET activity without becoming unable to act in Meatspace. |
| Access point | The physical entry point. The crew has to find, reach, and protect it. |
| Programs and hardware | Shape what the Netrunner can improve, defend against, attack, or recover from. |
Not every electronic device has a NET Architecture. The Core Rulebook specifically distinguishes systems that can be addressed with Interface from devices better handled with Electronics/Security Tech or Cybertech. This is a feature, not a dead end: it gives a Netrunner and Tech different ways to solve the same job.
A NET Architecture, End To End
Think of a NET Architecture as an elevator shaft of ordered floors. You cannot skip floors, although movement itself is not a NET Action. Every floor contains a reason to spend time, take a risk, or change the physical situation.
| Step | What happens | Why the crew cares |
|---|---|---|
| 1. Find it | The Netrunner uses Scanner to locate nearby access points in Meatspace. | The crew now has a physical objective, route, and defense problem. |
| 2. Get in range | The team reaches an access point and keeps the Netrunner in range. | Walls and distance matter; moving carelessly can force a dangerous exit. |
| 3. Jack In | The Netrunner spends a NET Action to enter the Architecture. | The job's electronic side begins while the physical team still has to hold the position. |
| 4. Read the route | Pathfinder reveals what lies ahead; Passwords can block progress. | The crew can decide whether to spend time, change plans, or create another opening. |
| 5. Clear or bypass floors | The Netrunner deals with programs, Black ICE, files, Control Nodes, and other obstacles in order. | Each success should affect a real object, secret, or threat in the scene. |
| 6. Take control | Control Nodes can operate connected systems such as cameras, doors, drones, alarms, or sprinklers. | The crew gets an immediate tactical or story advantage. |
| 7. Reach the bottom | At the deepest point, Virus can create a change that persists after the run. | The team can leave a lasting mark instead of merely borrowing access. |
| 8. Leave cleanly | Cloak hides traces; a deliberate Jack Out is safer than losing connection by distance. | The job's aftermath can be a clean escape, a delayed response, or a new enemy. |
The important distinction is between a temporary advantage and a persistent change. Control is lost when the Netrunner Jacks Out. A Virus at the bottom is the Core Rulebook's route for a lasting alteration, subject to the GM's ruling and the time needed to leave it.
Programs, Black ICE, And Demons
Programs are the Netrunner's active toolkit. The Core Rulebook groups non-Black ICE programs into Boosters, Defenders, and Attackers. A useful first deck is not the deck with the most aggressive options; it is the deck that helps the player answer the kinds of threats their GM actually puts in front of the crew.
| Type | What it does in play | The decision it creates |
|---|---|---|
| Booster programs | Improve a Netrunner's effectiveness in a relevant part of the Architecture while active. | Which capability is worth spending a scarce deck slot on? |
| Defender programs | Reduce or stop particular threats while active. | Is the run dangerous enough to reserve space for protection? |
| Attacker programs | Damage or disable an eligible program or Netrunner. | Is removing this threat worth the action and the program commitment? |
| Black ICE | Defends an Architecture or can be run by a Netrunner; it attacks people or programs according to its class. | Do you fight, Slide away, change pace, or get out? |
| Demons | Black ICE intelligent systems that use Control Nodes to defend a physical location. | What must the Meatspace crew handle while the Netrunner contests the system? |
Black ICE is not merely NET scenery. It can pursue a Netrunner through an Architecture, and the Core Rulebook makes unsafe exits especially dangerous. Demons connect the two halves of a job directly: they operate Control Nodes and can turn drones, turrets, or other connected defenses against the crew.
Keep The Whole Table In The Scene
Use this play pattern to keep a netrun moving at table speed:
- State the physical objective before anyone Jacks In: open the security door, stop the camera feed, extract the file, disable a drone, or change the elevator route.
- Give the Netrunner a visible access point and the rest of the crew an immediate reason to reach or hold it.
- Put at least one Control Node or file in the Architecture that changes the physical plan when found.
- On each NET turn, say what changed in Meatspace before moving to the next player.
- Let the non-Netrunners create time, cover, distraction, intel, or an alternate route instead of waiting for the run to finish.
- Decide whether the crew needs a temporary opening or has time to reach the bottom and leave a Virus.
For GMs, build the Architecture around the operation that owns it. A modest nightclub system may care about lights, cameras, doors, and a small Demon. A hardened lab may protect valuable files and lethal defenses. The Core Rulebook's Architecture procedure gives you the framework; the physical place gives the run its reason to exist.
What The Netrunning Deck Adds
The official Netrunning Deck guide describes the product as a 52-card visual aid: program, Black ICE, Demon, and floor cards that help players populate cyberdecks, build NET Architectures, and track a run. It does not add a separate rules engine or a new catalog of player options.
Use it when the table benefits from seeing the Architecture laid out on the table, when a GM wants to assemble a run quickly, or when the group loses track of which program, ICE, Demon, or floor is active. Skip it if a written map or digital notes already keep the scene clear. It is a clarity purchase, not a required expansion.
Gear Choices: Add Options With A Purpose
The Core Rulebook establishes the baseline deck, program, and hardware choices. Black Chrome adds equipment options, including an upgrade that grants an extra program-or-hardware slot to a Cyberarm-integrated Cyberdeck. That can be useful, but it does not replace the central decision: every slot you add should support the kinds of runs your campaign actually features.
If your group is not yet regularly running NET Architectures, do not buy gear to solve a problem the campaign has not created. If the runs are already a recurring job element, use the Cyberpunk RED Sourcebooks Guide to decide whether Black Chrome is the right purchase. A dedicated gear guide will join this library when it is live.
Where To Go Next
- Return to the Cyberpunk RED Guide Hub for the complete library map.
- Read the Cyberpunk RED Roles Guide for the Netrunner's place alongside the other nine Roles.
- Use the Cyberpunk RED Beginner's Guide when your group is still choosing a first-session path.
- Read Cyberpunk RED versus Shadowrun before comparing RED's job-site Netrunning with a cyberpunk-fantasy Matrix.
- Browse the Cyberpunk RED guide directory for every live guide.
The Cyberpunk RED Netrunner Role guide is live for Interface, first deck decisions, and crew coordination. The NET Architecture guide is live for local access points, floors, Control Nodes, Black ICE, Demons, and building a job-site run. The Netrunning Programs guide is live for Boosters, Defenders, Attackers, program tempo, and deck-slot tradeoffs. The Cyberdecks guide is live for capacity, program-and-hardware tradeoffs, upgrade context, and market access. The ICE guide is live for Black ICE, Demons, Slide, and shared NET-combat consequences. This is the live hub for framing a run and keeping the physical crew involved.
Sources And Scope
This guide summarizes the Netrunning chapter of the Cyberpunk RED Core Rulebook, the official Netrunning Deck guide, and the relevant Cyberdeck option in Black Chrome. It intentionally does not reproduce program lists, Black ICE statistics, Architecture tables, card text, or full rules procedures. Use those products for exact values and effects.
