The Egress Network comprises nodes that passively await commands for execution. These nodes can be any client capable of using WebSockets, though they are primarily deployed as browser extensions installed on end-user machines.
Nodes are any client that connects to the server to await commands for execution. Once connected, nodes passively await the next command, execute it, and return a response to the Server with no user intervention or interruption.
The Server process handles all communication to and from each node.
Manages deployed nodes that connect to the Server via an exposed WebSocket server. Nodes connect to the WebSocket server upon initialization and remain connected, awaiting commands.
Commands deployed nodes with bi-directional WebSocket messages via active connections available from the Manager. Commands are received via an exposed REST API, which provides endpoints for sending commands to any node, specific nodes, or all nodes at once.