Sign-in helpTalk to Fibmesh
Menu

One Network. One Fabric. One Platform.

Make the internet
your network.

Connect your people, apps and infrastructure over the internet you already have. Choose who gets access, what becomes public and where your internet traffic exits.

Explore the products Talk to Fibmesh

Availability depends on product, device and location. Talk to Fibmesh: Opens your email app.

Conceptual illustration of a laptop, an office and server infrastructure connected by one translucent woven fabric.
01 People02 Places03 InfrastructureConceptual illustration

Choose your connection

What do you
need to reach?

Select a job to see the path, its access boundary and the product behind it.

Fibmesh Networks

Available

The office network, wherever work happens.

An approved laptop reaches an office file server through Fibmesh and a supported gateway. The resource stays private.

Explore Networks ↗
Routing & access details

The path

  1. Approved laptop
  2. Fibmesh node
  3. Office or cloud resources

Connections are delivered through Fibmesh nodes.

Connection details

Devices join individually. A gateway connects permitted resources on a LAN. Each connection follows your access rules; applications keep their own login.

Fibmesh Publish

Available

Keep the app where it is. Give people a link.

Publish gives a web app or API on localhost, a server or a private LAN its own HTTPS address. Visitors open the link in a browser; they do not need to join your private network.

Explore Publish ↗
Routing & access details

The path

  1. Visitor opens your URL
  2. Fibmesh HTTPS gateway
  3. WireGuard → connector → app

See product details for availability and setup.

Connection details

The public hostname points to Fibmesh. Its gateway receives the request and forwards it through a tunnel to your connector, then to the selected application. Separate apps can have separate links; your app still handles its own authentication.

Fibmesh Public IPs

Available

Your server. Your location. A public address.

A supported server receives a public address over its existing internet connection. Incoming rules decide which services are reachable.

Explore Public IPs ↗
Routing & access details

The path

  1. Internet or partner service
  2. Fibmesh public address
  3. Your device or gateway

Supported device and gateway delivery

Connection details

Choose inbound access, selected outbound destinations or full-tunnel routing. Incoming connections are controlled separately by firewall rules. Replies to permitted incoming connections return through Fibmesh; unrelated outgoing traffic follows your selected routing policy. Device addresses can be dual-stack or IPv6-only where supported.

Fibmesh Outbound

Available

A different connection. A familiar exit address.

A supported device reaches an external service through a Fibmesh exit. A stable address, where agreed, can support IP allowlisting.

Explore Outbound ↗
Routing & access details

The path

  1. Your device
  2. Fibmesh exit
  3. Internet services

An outbound exit does not make the device publicly reachable.

Connection details

Full-tunnel routing carries eligible internet traffic through the exit. The current model uses one active organisation profile, with platform and local-network exceptions. It does not provide per-app or selected-destination routing.

Public IPs assigns an address to your infrastructure; Outbound provides an internet exit. Either may meet an outgoing source-address requirement—you may only need one.

Compare products ↗

Security & responsibility

Know what protects
each connection.

Device identity and access rules define the permitted path. Encryption and application security protect different parts of the journey.

Encrypted tunnel paths

WireGuard protects supported tunnel segments. Use application encryption beyond the tunnel where needed.

Keys stay local by default

Private endpoint keys remain on the device.

Your application keeps its own permissions

Application logins and data permissions remain essential, even on a private connection.

How the platform works ↗Read the security boundaries ↗

From real deployments

Keep the server.
Extend its reach.

Two anonymised deployments show how a public address can connect existing infrastructure to the people who need it.

Illustrative restaurant interior with a point-of-sale terminal on the counter.
Illustrative setting · Restaurant operations

Restaurant operations / Public IPs

One billing server.
More than one location.

A restaurant business kept its billing server at one site. A Fibmesh public address let another location reach the same application.

Illustrative on-site IT room with a compact server cabinet and a maintenance laptop.
Illustrative setting · On-site infrastructure

ERP delivery / Public IPs

On-site software.
A provider-independent address.

An ERP provider ran Fibmesh on customers’ Windows servers. Public addresses came from Fibmesh, independently of each site’s broadband provider.

Both deployments used full-tunnel routing on the application host. This describes those hosts, rather than every device at each site.

Explore the deployments ↗

From Fibmesh

Ideas worth connecting.

Read all articles ↗

Before you start

A few things
worth knowing.

Can I connect equipment on my LAN?

A supported gateway can connect permitted LAN resources, such as servers, storage or equipment, without installing Fibmesh on each resource. Routing and application compatibility still need to be checked.

See deployment options ↗
What can I use today?

Networks, Publish, Public IPs and Outbound are available. Contact Fibmesh to arrange setup and confirm the devices, features and locations for your deployment.

Check availability ↗

Start with your setup

Tell us what
needs to connect.

Share your devices, applications and locations. We’ll help you identify the right product and plan your setup.

Talk to Fibmesh Assisted setup. Opens your email app.Discuss a business pilot ↗