Put the gateway first
A homelab topology needs one obvious gateway before anything else is added. In HLBuilder that usually means placing the router node first and giving it the network role that other devices can reach.
This prevents a common planning mistake: adding servers, storage, and Wi-Fi gear before deciding where the lab enters the rest of the home network. The router position gives the rest of the diagram a direction.
Use the switch as the wired backbone
The switch node should collect wired devices that need stable connectivity. Servers and NAS devices should usually appear on the switch side of the diagram, not behind the access point or a random branch.
HLBuilder supports switch nodes as separate components, so a user can reason about uplinks and device count before choosing a specific switch from the catalog.
Label the branches by use
A small topology is easier to read when branches have a purpose. One branch can hold storage, one can hold service hosts, and one can hold wireless clients. The diagram does not need to be large to be useful.
When the topology is saved, network calculation has real nodes and edges to read. That is better than trying to assign addresses from a list that does not show how devices connect.
Builder checks
Check
Router node exists before network calculation is run.
Check
Switch node is connected to the router, not left as a standalone item.
Check
Servers and NAS devices sit on wired branches.
Check
Access point is visible as its own node instead of hidden in notes.
Common questions
Does every homelab need a managed switch?
No. A managed switch is useful when the plan needs separation, PoE, or more control, but a small first lab can start with the switching hardware already available.
Why draw the switch separately?
A separate switch node shows uplinks, wired capacity, and which devices depend on the same backbone.