The short answer
A Netrunner gives the crew new ways to change the physical job: doors, cameras, drones, files, and escape routes. Interface turns a reachable NET Architecture into access, information, control, and a hold on the site that can outlast the run. 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.
Hot take
Judge a Netrunner by how often their success hands the whole table a better decision. Invisible wins inside the Architecture count for little on their own.
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, sets how many NET Actions the Netrunner takes on a Turn, and grants the Interface Abilities. No other Role can do this, so Interface is the Netrunner's whole reason to be on the job, not a bonus to general computer skill.
Net actions by interface rank
| Interface Rank | 1 to 3 | 4 to 6 | 7 to 9 | 10 |
|---|---|---|---|---|
| NET Actions per Turn | 2 | 3 | 4 | 5 |
A starting character begins with their Role Ability at Rank 4, so a new Netrunner takes 3 NET Actions a Turn. Rank 7 is the next jump, which makes it the first big Improvement Point target.
The nine interface abilities
| Ability | What it lets the Netrunner do |
|---|---|
| Backdoor | Break through Passwords and other obstacles in the Architecture. |
| Cloak | Hide their actions in the Architecture before leaving. |
| Control | Operate things attached to the Architecture, such as cameras or doors. |
| Eye-Dee | Learn what a found piece of data is and what it is worth. |
| Pathfinder | Learn the map of the Architecture. |
| Scanner | Find the physical locations of access points in an area (a Meat Action). |
| Slide | Slip away from one Black ICE that is following them. |
| Virus | Leave a custom virus at the core of the Architecture. |
| Zap | Make a basic attack against Programs and enemy Netrunners. |
Most Interface Ability checks use Interface + 1d10 against a DV; Zap is an attack instead. Every higher Rank still makes the whole set more reliable. Scanner is the one to use before the job, since it tells the crew where the access points are.
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.
What a Netrunner needs to run
The Core Rulebook's kit list is short:
- Neural Link and Interface Plugs. A cyberdeck connects through Interface Plugs, and the plugs require a Neural Link. Every Netrunner has at least this much cyberware.
- A cyberdeck. Programs and Hardware share the same slots. A Poor Quality Cyberdeck has 5 slots (100eb), a standard Cyberdeck has 7 (500eb), and an Excellent Quality Cyberdeck has 9 (1,000eb). A Netrunner can be plugged into only one deck at a time, and switching decks takes a Meat Action.
- Virtuality Goggles (100eb). They overlay the NET on the Netrunner's real surroundings so they can still move and take cover. Forget them, and the Netrunner is effectively Unconscious to the physical world until they Jack Out.
Two options are worth knowing early. A Bodyweight Suit is SP11 armor that stores the deck and adds one Hardware-only slot, and a Cyberdeck Cyberarm option builds the deck into a Cyberarm for one extra slot.
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.
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.
The access point is the whole crew's objective
In Cyberpunk RED, the Netrunner must get within 6 m/yds of one of the Architecture's access points to Jack In, and a wall in between usually blocks the connection. Moving out of range while jacked in throws them out of the Architecture and leaves them exposed, and a clean Jack Out resets the Architecture's defenses, so the run starts over next time. 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 escaping now and a hold on the system later. | 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.
For deck and software detail, read the Cyberdecks Guide and the Netrunning Programs Guide.
Sources and scope
This guide summarizes the Netrunner, Interface, Cyberdeck, and Netrunning material in the Cyberpunk RED Core Rulebook. It lists NET Actions by Rank, the Interface Abilities in short form, and the base cyberdeck options, but does not reproduce program lists, hardware lists, Architecture tables, or full rules procedures. Use the Core Rulebook for exact rules and values.
