Cascades Theory PRO

Why cascades and node chains are needed

To many, a cascade is "when one node isn't enough." It's actually about something entirely different: separating the entry point and the exit point so that a block of the entry doesn't kill the service and the exit stays white. Let's break down what a chain of nodes gives, when it's needed, and when it only hurts — no configs, pure mechanics.

Go to practice →

This material is about engineering your own infrastructure and is educational in nature. Complying with the laws of your own jurisdiction is on you.

What a cascade is

A cascade (a.k.a. multihop) is a chain of two or more nodes: client → entry → exit → internet. The client sees only the entry's IP. Sites see only the exit's IP. Between them is your internal link, which no one on the outside suspects.

A direct node is simpler: the client connects — and exits to the outside from that same IP. One point,…

This guide is part of paid access

Get full access to unlock the text, configs and builder.

Unlock access →