Select an intrusion point, review its objectives, and configure your response loadout.
ClearanceInitiate
Campaign stars0 / 36
Incidents contained0 / 12
Next directiveRapid Provisioning · 4 stars
Available connectionRegion bridgeDrag to pan · Wheel or pinch to zoom
Response Configuration
Configure your loadout
Choose your defence modules and one Last-Line. Response directives may alter the permitted loadout.
Threat ForecastLoading signatures
Defence modules5 / 5 selected
Last-LineChoose one ultimate defence
Response DirectivePersistent campaign reward
Incident Report
Incident contained
Preparing anonymous balance report…
Intelligence
Threat Database
Learn how each hostile process behaves and which systems counter it.
Threat families and countersDefence module roles
Page 1 of 1
Operator Record
Firewall Protocol Profile
Operations Manual
How to Play
Deploy and specialize
Build: Select a module, then place it near a route. Node modules use one eligible router or relay slot and ignore normal spacing.
Upgrade: Level two locks one of two paths; level three activates that path's capstone.
Recover: Selling returns the full base cost plus 60% of upgrade spending. Last-Lines can reposition between waves.
Traffic, Bandwidth, and Uptime
Throughput: Route redundancy controls healthy-traffic Processing and gradually affects Uptime.
Bandwidth: The limit is soft. Every point over lowers the live Uptime ceiling; four over leaves 1%.
Uptime: A score and objective rating affected by Throughput and breaches. It never weakens modules.
Read and counter threats
Open the configuration forecast, compare each threat family with your module roles, then launch the wave.
The red ingress zone reduces incoming module damage by 70% and effects by 90%. Hostile abilities activate after threats leave it.
Armoured traffic needs Precision or Intel coverage. Carriers release payloads; Echo Packets duplicate unless revealed, contained, or blocked by an Arc Relay.
Routing, zones, and Last-Lines
Closing routes creates choke points but costs switches and reduces Throughput. The control plane prevents stranded services.
Marked deployment sectors may allow or require specific modules. Read each zone before placing.
Bring one Last-Line, deploy it once, and time its manual ability around the long cooldown.
Preferences
Settings
Every level attempt sends an anonymous gameplay balance report containing wave, economy, threat, and defence performance to private backend storage. Reports never contain your account, email, username, IP address, or typed input. A report remains in the browser only while an unsuccessful upload is waiting to retry. When signed in, a separate account record stores your incident results, usage totals, and achievements for profile sync and leaderboards.
Global Top 10
Incident Leaderboard
Loading scores…
Processing450
+0 projected
Bandwidth0 / 16
Soft capacity limit
Throughput100%
Live route capacity
Uptime100%
Score and objective rating
Wave0 / 10
Score0
Switches3 / 3
Portrait play uses a larger pannable battlefield. Drag sideways, or rotate your device for the full network view.
Training 1 / 11
Protocol Basics
T
New Threat Detected
Threat
Module deployed.
Economy Report
Wave contained
Incident waveWave 1
Hostile traffic inbound
Defence Modules
Build palette
1–0 select · Space launches/pauses · Escape cancels
About the Game
Defend a living network
Firewall Protocol is a network-routing tower defence game with twelve campaign
incidents, specialized deployment sectors, persistent progression, and response directives.
Core Objective
Maintain network uptime
Defend the Database, Communications service, and Core. Read each threat forecast,
bring explicit counters, deploy within marked sectors, and use routing to create
strong defensive choke points.
Early Access
Help tune the protocol
This is an active prototype. Runs contribute anonymous balance data so difficulty,
modules, threats, and incident pacing can improve with real play.