Sign-in helpTalk to Fibmesh
Menu

Business IT

One organisation. More places to work.

Connect approved people, offices and cloud resources over existing internet connections. Keep private access, public services and outgoing routing deliberate.

Plan a team deploymentExplore Networks →

Connection paths

Connect people, places and approved resources.

Follow the connectionIllustrative connection paths

Connect the organisation around the resources it uses.

  1. Remote employeeSupported enrolled deviceWireGuard
  2. Fibmesh routing nodeIdentity and permitted routesWireGuard
  3. Office / cloud gatewaySelected destination rangesPrivate network
  4. Business resourcesApps, storage and devices

Networks provides a private path across existing internet connections and providers. A site or cloud gateway can bring approved subnet resources within reach.

This is routed connectivity, not one broadcast LAN or a dedicated cloud circuit. Each destination needs a working return path and the appropriate application permissions.

Explore Networks →

Expose the service that needs an outside audience.

  1. Partner systemUses a public service endpointApplication traffic
  2. Fibmesh public deliveryPublic address + firewallWireGuard
  3. Business server / gatewayTunnel delivery to the target

Use Public IPs for an address-based service that an external system must reach without enrolling into your private network.

For browser-facing applications, Publish offers a hostname-based alternative. Public reachability requires authentication, patching and an explicit inbound policy.

Explore Public IPs →

Choose the source external services see.

  1. Company device / routed LANEligible outgoing trafficWireGuard
  2. Fibmesh exitSelected internet exitInternet
  3. Cloud / SaaS serviceObserved public source

Outbound serves internet-routing needs. Public IPs is another option when a specific allocation or selected-destination source identity is the central requirement.

Outbound’s current profile model is full tunnel. Do not assume destination-by-destination rules, concurrent department profiles or a verified kill switch.

Explore Outbound →

Put it to work

Build the network around a distributed organisation.

A company’s resources no longer sit behind one office router. People move between locations, applications run in different clouds, and some equipment stays on site. Fibmesh gives these connections a common place to be managed, while each resource keeps its intended audience.

Give staff a path to work

Use Networks for approved access to applications, servers, storage and supported peripherals. People can join with supported devices; sites can join through gateways.

Work from anywhere →

Connect offices and clouds

Keep resources with the providers and locations that suit them. Use Networks through supported hosts or gateways for selected private routes between working environments.

Hybrid cloud networking →

Connect to external systems

Use Public IPs for server reachability, or an agreed Outbound source for a cloud or SaaS allowlist. Choose incoming and outgoing policies deliberately.

Stable outgoing identity →

Keep incoming services separate from outgoing routing. Current Outbound profiles use full tunnel; confirm platform and address-family support before changing staff traffic. Compare the connection options →

Illustrative collaborative office environment
Illustrative photography · not a photograph of the described customer or deployment.

Your first working result

One team reaches one approved application.

Build the first rollout around a useful working path. Verify private resource access independently from public service exposure and outgoing internet routing.

  • Use the real application from a supported device
  • Verify both permitted and denied resource access
  • Record the owner, recovery process and removal procedure
Explore working across locations →

A practical first deployment

Prove one end-to-end working path.

  1. Inventory people and resources

    Choose a team, supported devices, one application and any gateway. Record destination ranges, application accounts and the person responsible for the resource.

  2. Choose private and public paths

    Start with the minimum required access. Separate resource access from internet routing; connecting a private network does not inherently reroute everyone’s browsing.

  3. Verify and expand

    Check permitted and denied access, return routing, actual application use, loss of connection and removal. Add another site or service after that path is understood.

Questions, answered

Before you connect.

Is this a replacement for our ISP or a private leased line?

No. Fibmesh runs over supported existing connectivity. It does not provide an access circuit, dedicated cloud interconnect or a blanket performance guarantee.

Can printers, scanners and storage be reached remotely?

Supported IP services can be reached through an approved gateway route. Drivers, application support and permissions still apply. This is not automatic broadcast discovery, USB sharing or a local Ethernet extension.

Can we give different departments different Outbound profiles?

The current Outbound implementation supports one active profile per organisation. Do not assume simultaneous department-specific exits or a complete per-application routing policy.

What about identity, security and automation?

An enrolled device has its own identity; reaching a resource also requires the relevant permission and application login. Security explains the trust boundaries, and the developer reference describes current CLI/API scope. Confirm specific enterprise controls and contractual commitments before procurement.

Bring a representative team, one resource and your network constraints. Build a rollout plan from the connection you can demonstrate.

Plan your first deployment →