One network · different permissions
Give each group the access its work needs.
The same people and resources. Select a group to see its example access.
Engineering
Engineers reach development resources across two cloud environments. Their working location and access provider can differ; the approved resource scope stays with the group.
- Permitted resources
- Cloud build server and project workstation
- Outside this group
- Office business systems
Operations
An operations colleague reaches the office application from a supported mobile device. Gateway routing brings the approved site resource into reach; it does not open the whole office LAN.
- Permitted resources
- Office business systems through an approved gateway
- Outside this group
- Build server and project workstation
Contractor
A collaborator works on one project resource. Remove their membership when the engagement ends, without moving the workstation or changing everyone else’s access.
- Permitted resources
- Project workstation only
- Outside this group
- Office business systems and build server
Illustrative access model. Lines represent approved relationships, not physical links, direct peer-to-peer tunnels or measured traffic. Application login still applies. Device, mobile and gateway support require a verified release.
Two ways to join
Connect a device. Bring a location.
Enrol a device
A supported laptop, mobile device, server or compute host runs the Fibmesh app or agent. It receives its own device identity and private address.
Connect a location
A supported gateway or router provides a path to selected office, branch or cloud resources. Equipment behind it keeps its existing LAN address.
A gateway reaches only the resources and routes you approve. It does not enrol every device behind it.
Compare devices, routers and site gateways →What your team can reach
Which resources need to be within reach?
Across the office. Across providers.
The files can stay here.
The work can happen anywhere.
Explore private storage access →Applications and compute
Internal tools, servers and specialist workstations. Reach the resource while keeping its application login and host firewall in place.
Files and storage
Office file servers and NAS devices. Work with the files you have permission to use, without moving the storage.
Network peripherals
Compatible network printers and scanners through an approved gateway. Drivers and discovery may need separate setup.
Names and routing
Find resources by name. Understand their path.
Private workspace DNS helps supported clients find approved resources by name. Network permission still applies when a name resolves.
The current architecture connects through Fibmesh routing nodes. Direct P2P is planned. Private IPv6 belongs to the product scope; assignment support must be confirmed for the deployed release. Private resource access and internet routing through an exit are separate choices.
See how Fibmesh Networks works →Guides for your setup
Plan the deployment around your work.
- Work across home, office and mobile connections →
- Connect selected cloud and office resources →
- Reach private files and storage →
- Prepare a contractor’s first day and remove access at handover →
- Reach approved NVRs, appliances and IoT services through a gateway →
- Plan office and branch access →
For scripting and administration, see Networks CLI and API scope. Explore all use cases →
Before you begin
Bring a real use case. Start with a small network.
Does this replace our internet connection?
No. Fibmesh uses your existing internet connections. “Global” describes a network across locations and providers; it does not promise an owned worldwide backbone or availability in every country.
Will it work exactly like being in the office?
It provides a private path to approved resources, not a flat Ethernet LAN. Application accounts still apply. Network discovery, printer drivers and scanner protocols need assessment; USB-only peripherals require a separate sharing solution.
Which devices and gateways can we use?
Check the supported native release, platform and market before deploying. Mobile devices join as clients. Router compatibility depends on the model and software; a Fibmesh edge gateway is a proposed option. Hardware remains in development.
Check availability and prerequisites →Start with the people, locations and resources you want to connect. Use the first-network guide to prepare your evaluation.
Request access →