Start with the decision you need to make
Who starts the connection?
A visitor opening your app and a worker calling a provider need different network arrangements. Replies are part of both.
Inbound or outbound →A link or a routed address?
Compare a hostname for one web application with public addressing for a device, gateway or subnet.
Publish or Public IPs →Which traffic should use Fibmesh?
Both Public IPs and Outbound can support a recognised source address. The routing scope helps decide which one fits.
Public IPs or Outbound →Decide where the connection runs
A laptop can join directly. An office can join through a gateway that reaches approved LAN resources. A web app can use a connector on its host or a suitable machine on the local network. The right method depends on the product, operating system and what the software must reach.
Compare connection methods → Plan your first private network →Work through a real deployment
Start with a private team network, a file server across locations, a provider allowlist or an application you want to run on your own infrastructure. Each scenario explains the participating resources and the boundaries to keep.
Browse worked use cases →Write a useful brief
Record who starts the connection, the target and port, which address the other party must see, and what traffic should stay on the existing ISP. Include operating systems, the device or gateway owner, address-family requirements and the intended service location. That gives the setup guide a concrete job to solve.