Fibmesh NetworksAvailable
Reach private apps, files and infrastructure across your existing internet connections.
One network. Deliberate permissions.
The engineer, the operations colleague and the contractor can belong to the same organisation without reaching the same resources.
Give engineers access to the build server and project workstation. Their working location and internet provider can differ; the approved resource scope stays with the group.
A colleague reaches the office application from a supported mobile device. The gateway brings that resource within reach without opening the whole office LAN.
A collaborator gets a path to one project workstation. Remove their membership when the engagement ends; the resource stays where it is.
This illustration shows approved relationships, not live traffic or direct peer-to-peer tunnels. Application login still applies.
Across locations. Your existing internet providers.
Access with a purpose. Only the resources you permit.
Your applications. Their logins and permissions stay.
Two ways to join
Start with the person or resource that needs a connection. Use a supported app on the device, or a gateway for approved resources at a location.
Explore devices & gateways →A supported computer, mobile device, server or compute host runs the Fibmesh app or agent. It has its own device identity and private address.
Use the supported app or agent for that device’s operating system.
A supported gateway or router provides approved paths to office, branch or cloud resources. Equipment behind it keeps its existing LAN address.
A gateway does not enrol every device behind it or open the whole network.
Start with the work
Keep your tools and infrastructure. Plan a private connection around the job you need to do.
Home, office and supported mobile clients.
Reach private file servers and NAS resources.
Approved resources across clouds and offices.
One project resource, with a clear handover.
Approved NVRs, appliances and IoT services.
Plan office and branch access through a gateway.
Application authentication and host firewalls still apply. Compatible network printers and scanners can need separate driver or discovery setup. Network access does not provide file synchronisation or backups.
Private workspace DNS helps supported clients find resources by name. Resolving a name does not grant permission to connect.
Current connections pass through Fibmesh routing nodes. Direct P2P is planned. WireGuard protects supported tunnel segments; applications need appropriate protection beyond them.
Private access does not require an internet exit. Private IPv6 is within the product scope; confirm assignment support for the deployed release.
Before you begin
No. Fibmesh works over your existing internet connections and across supported providers. A network across locations does not promise a worldwide backbone or availability in every country.
Networks provides approved private paths, not a flat Ethernet LAN. Application accounts remain in place. Local discovery, printer drivers and scanner protocols need assessment; USB-only peripherals need a separate sharing solution.
Confirm the native release, platform and market before deploying. Mobile devices join as clients. Router support depends on its model and software. A Fibmesh edge gateway is a proposed option. Hardware remains in development.
Check availability and prerequisites →Your first network
A person. A private resource. A clear permission. Build the network around that first.
