Skip to content
Farlec docs

Networking

Private networks, public ports and web routes.

2 min read Updated

Public web routes#

Each machine declares app ports at create time (up to 16). Publishing a port from the machine's Routes section mints a public HTTPS URL:

https://<route-id>.farlec.app

Traffic terminates on Farlec's edge and forwards to the guest port. Unpublishing removes the URL. Public-side firewalling beyond that is the guest's own concern.

Private networking#

Every Farlec machine sits on our private network. Our nodes are connected at layer 2, so your machines talk over a true private fabric.

  • No tunnelsTraffic between your machines crosses a dedicated internal fabric. It is not a VPN or an overlay network. There is nothing to install, no keys to manage, and no encapsulation eating your speed.
  • Isolated by defaultMachines are born unreachable. The platform enforces an allowlist per machine, so only machines you link can reach it. Not the public internet, not other customers, not even your own machines until you link them.
  • Cross region includedA machine in one region talks privately to a machine in another. The link is the same either way.

Open the machine drawer's Network tab and pick another one of your machines. Links are symmetric and stored once per pair. Raw IP entry is never accepted; the platform supplies the addresses.

  • A machine can hold up to 10 links.
  • Unlinking removes the pair's connectivity. The network state converges within a minute.
  • Collaborators never see or manage the private network. Linking is owner only.
  • Deleting a machine removes its links automatically.

Guest firewall#

Farlec enforces the private-network rules described above; anything beyond that — host firewalls, fail2ban, service binding — is the guest's own business. Bind services to the private interface (or a published route) rather than assuming public reachability.