Cyberpunk RED Guide Hub | Cyberpunk RED Roles Guide | Netrunning Guide | Gear Guide
The Short Answer
A Netrunner does not leave the crew behind to play a separate game. A Netrunner gives the crew new ways to change the physical job. Interface turns a reachable NET Architecture into access, information, control, and lasting leverage. The cyberdeck determines which tools come along; the crew determines whether the Netrunner gets the time and safety to use them.
Start each job with one shared sentence: "If the Netrunner succeeds, this changes." Open the loading door. Blind the cameras. Stop the drone. Extract the evidence. Turn the elevator into an escape route. That sentence is more important than a perfect deck list.
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 best Netrunner is not the one who wins the most invisible fights. It is the one whose success gives the whole table a better decision.
If a run only changes numbers on a private map, it will feel disconnected no matter how clever the program choice is. If it opens a path, reveals a betrayal, turns off a threat, or forces an enemy to react, every player has something to do with the result. Build the deck and the Architecture around that shared moment.
Interface Makes A Netrunner A Netrunner
The Core Rulebook defines Interface as the Netrunner's Role Ability. It enables Netrunning, establishes how many NET Actions the Netrunner can take on a turn, and provides the related Interface abilities. That means Interface is not a generic computer skill bonus. It is the Role-specific capability that lets the character operate inside a NET Architecture.
At the table, Interface connects to a chain of practical choices:
| Before the run | During the run | After the run |
|---|---|---|
| Find and reach a physical access point. | Choose where to spend NET Actions and what obstacle or Control Node matters now. | Decide whether to leave traces, preserve access, or create a lasting change. |
| Agree on the physical objective with the crew. | Tell the crew what has changed in Meatspace. | Live with the attention, evidence, or enemy the run created. |
The Cyberpunk RED Netrunning Guide explains the job-site NET procedure. The NET Architecture Guide covers local access points, floors, Control Nodes, Black ICE, Demons, and a small build workflow. The Cyberdecks Guide covers capacity, programs-and-hardware slots, upgrades, and market access. The ICE Guide covers Black ICE, Demons, Slide, and shared NET-combat consequences. This guide focuses on the Netrunner's decisions inside that larger job.
Start With A Small, Purposeful Cyberdeck Loadout
A cyberdeck holds programs and hardware, so every choice is a choice about what kind of run the Netrunner expects to face. Do not begin by trying to answer every possible threat. Begin with the recurring job your group actually plays.
| Campaign pattern | Loadout priority | Question to ask before filling a slot |
|---|---|---|
| Infiltration and extraction | Tools that help the crew locate, enter, and control the systems tied to a location. | Which door, camera, alarm, or route will this change? |
| Investigation | Tools that help find, access, protect, or leave with information. | What evidence does the crew need, and who notices it missing? |
| Hostile corporate sites | Protection and a plan for serious opposition inside the Architecture. | Can the physical crew create time if the run goes badly? |
| Recurring defense problems | Options that support the group's usual answer to drones, cameras, or controlled systems. | Is this a real campaign pattern, or a hypothetical fear? |
Programs fill distinct roles, including boosters, defenders, attackers, and Black ICE interactions. Hardware changes the deck's practical options. Use the Core Rulebook for the exact program, hardware, capacity, cost, and rules details. The important first decision is whether each slot supports a job the crew expects to take.
The Access Point Is The Whole Crew's Objective
In Cyberpunk RED, the Netrunner must reach a physical access point. That requirement is a feature: it gives the rest of the crew a real reason to scout, sneak, negotiate, create a distraction, protect a position, or choose an alternate route.
Use this pre-run checklist:
- What is the physical objective the Netrunner's work will change?
- Where is the likely access point, and who can get the crew near it?
- What is the crew doing while the Netrunner is connected?
- What tells everyone the objective is complete?
- What is the extraction plan if the Architecture or the physical location turns hostile?
Those questions stop a netrun from becoming a pause in the action. They turn it into a scene where the Netrunner has a technical path and everyone else has a physical problem worth solving.
Coordinate The Run In Short Callouts
Keep the team synchronized by making the Netrunner's updates concrete.
| Netrunner callout | What the rest of the crew learns | Useful response |
|---|---|---|
| "I found the camera control." | The system is real and nearby. | Move while the blind spot exists. |
| "There is a defense program between us and the door." | Time and safety are now scarce. | Hold the access point, draw attention elsewhere, or find another route. |
| "The elevator is ours for a moment." | The physical plan has changed. | Move the client, gear, or crew before control is lost. |
| "I can leave a deeper change, but it takes time." | The crew must choose between escape and long-term leverage. | Decide whether the future payoff is worth the present risk. |
The Netrunner does not need to narrate every rule step. State the consequence in Meatspace, ask what the crew does with it, and then return to the next player. That rhythm keeps Interface at the center of the operation without making it the only thing happening.
Gear Is A Job Decision, Not A Shopping Race
The Core Rulebook establishes the baseline cyberdeck, program, and hardware rules. Use the Cyberpunk RED Gear Guide to find source-aware equipment guidance and the Cyberware Guide when the setup involves a Neural Link, Interface Plugs, Cyberarm integration, or another prerequisite.
Before adding a deck option, check five things:
- What recurring job does it improve?
- What deck capacity or prerequisite does it consume?
- What existing tool would it replace or crowd out?
- Does the campaign actually feature the run that justifies it?
- What resource, downtime, or story consequence does the purchase introduce?
More capacity is only useful if it supports a real choice. A focused deck that makes one type of job more reliable is usually more memorable than a broad collection of tools the table never uses.
Play The Person Behind The Deck
Interface explains what the character can do in an Architecture. It does not decide why they do it. Give the Netrunner a reason to care about the data, a history with a system, a contact who needs access, or a boundary they will not cross for a client.
That roleplaying choice gives the GM material to work with after the run. A stolen file can matter to somebody. A clean exit can earn trust. A traced intrusion can create a threat. A system left intact can become a future route. The character's choices turn technical access into a campaign story.
Where To Go Next
Read the Cyberpunk RED Netrunning Guide for the system-wide NET procedure, the NET Architecture Guide for job-site security design, and the Gear Guide for source-aware deck and equipment choices. Return to the Roles Guide to compare the Netrunner with the other Roles, or use the Cyberpunk RED Guide Hub and guide directory for the full live library.
Dedicated guides for programs, cyberdecks, and ICE will link from the Netrunning hub when they are published.
Sources And Scope
This guide summarizes the Netrunner, Interface, Cyberdeck, and Netrunning material in the Cyberpunk RED Core Rulebook. It does not reproduce Interface ranks, NET Action values, program lists, hardware lists, cyberdeck statistics, Architecture tables, or full rules procedures. Use the Core Rulebook for exact rules and values.
