Use cases

Work through a real connection problem.

Plan private access, application publishing, public addressing and internet exits. Worked examples explain resources, permissions, verification and removal.

Worked planning examplesDesign reference
A connection plan has a beginning and an end.
Situation

Source, destination and application owner.

Boundary

The permission and direction that change.

Proof

Allowed path, blocked path and clean removal.

Illustrative model · release and service scope are assessed separately.

Worked planning examples

See what goes into a connection plan.

Each scenario names its resources, permission boundary, test evidence and removal criteria. These are planning examples rather than claims about customer deployments.

Private resources

Keep the working environment inside the team

Plan a build host or project tool around approved identities and application authentication.

Private infrastructure

Keep the resources. Connect the people who need them.

Private storage and compute across providers can belong in the same organisation network, with a defined owner and access boundary.

Public and provider-facing

Give the right party the right entry

Publish one HTTP application or make a provider see the approved outgoing source.

Networks and movement

Account for the path and its restoration

Distinguish private access from broader routing; account for gateway networks and return paths.

Separate invitation-led service · Public IPs

Several workloads. Their own public addresses.

A small hosting operator or virtualisation lab may need a public block for several servers, VMs or containers. Routed Subnets provides the path: Fibmesh routes the assigned block over a tunnel to a customer-owned router, which forwards it to the workloads.

The worked model covers small IPv4 blocks, IPv6 prefixes, firewall boundaries and return routing. IPv4 and IPv6 are separate allocations, with IPv6 prefixes from /48 through /64. This invitation-led managed service is scoped separately from the app MVP.

Explore the routed-subnet model →

Your next decision

Use the scenario as a working document.

Replace the example resource names with your own. Record the source and destination, assign each responsibility and choose one negative test. Keep the removal criteria: a useful plan should show how the connection ends as clearly as how it starts.

Planning a whole location? Explore offices and branches →

Compare the product decisions →

Keep what you already run

Your hardware. Your customer sites.

Run on your own infrastructure

Connect local servers, GPU hosts and colocated workloads to their users and external clients.

Explore self-hosting and uncloud →

Equipment and IoT

Bring approved access to NVRs, NAS, kiosks and equipment that cannot run an agent.

Explore equipment connectivity →