Networks
A private network for people, locations and clouds.
- Devices & gateways
- Private routing nodes
- Private resources
- You connect
- Supported computers, phones and servers join individually. Gateways connect approved resources on an existing LAN.
One Network. One Fabric. One Platform.
Four ways to connect your world.
A private network. A public web URL. An assigned IP. An internet exit. Choose the connection your people, apps and infrastructure need.
Use the product that fits. Fibmesh does not require all four.
Explore the four products
Publish
An HTTPS URL for an application you host.
- Visitor
- HTTPS gateway
- Software connector
- Local app
- You connect
- A connector beside the app, or an Edge connector on its LAN. Visitors use a browser or API client.
Public IPs
Public addresses and routed subnets delivered to your infrastructure.
- Incoming connection
- Public IP delivery
- Assigned public IP
- You connect
- A supported device or gateway, or a router for a routed subnet. Set incoming rules and outgoing routes separately.
Outbound
An internet exit over your existing connection.
- Internet traffic
- Internet exit
- External service
- You connect
- A supported endpoint or a deliberately configured gateway. The current profile model uses full-tunnel routing.
Choose for the job
Some requirements have more than one good answer.
A web URL, an assigned IP and an internet exit solve different problems. For outgoing identity, the right choice depends on how you want the address delivered and which traffic should use it.
Swipe sideways to see all columns.
| What you need | Start with | Why it fits |
|---|---|---|
| Private access for people, devices or locations | Networks | Approved devices reach private resources across existing providers, directly enrolled or through supported gateways. |
| A browser link or HTTPS endpoint for your app | Publish | Map a web URL to a selected HTTP application. Visitors do not need a Fibmesh client. |
| Public address access to a server, gateway or subnet | Public IPs | Deliver public addresses to your infrastructure. Choose protocols, incoming rules and routing within the supported service. |
| A source address an external provider recognises | Either Public IPs or Outbound | An assigned IP can be the source of outgoing traffic; an agreed stable exit can do the same. Choose one delivery model that meets the requirement. |
| Only selected outgoing destinations use an assigned IP | Public IPs traffic modes | The supported selected-outbound mode scopes destinations. Outbound’s current profile model uses full-tunnel routing. |
| Route a device’s eligible internet traffic through an exit | Outbound | Manage an exit profile without requiring the exit’s public address to be installed on the device. |
One organisation / separate needs
The same server can serve different audiences.
Imagine a company running a customer portal on its own server. Staff need private administration, customers need the portal, and a background job calls an external API.
YOUR OFFICE OR CLOUDOne application server
Portal · administration · integration worker
Private administration
Networks gives approved staff a private path to the server. Application accounts still determine what they can do.
Explore Networks →A public web URL
Publish exposes the selected portal through an HTTPS hostname. Customers use the application login.
Explore Publish →A recognised outgoing source
Choose Public IPs or Outbound if the provider requires a source-IP allowlist. Check traffic scope and the return path before combining capabilities.
Work through allowlisting →Illustrative design, not a verified combined deployment. Each connection needs its own policy and compatible routing. There is no need to buy both Public IPs and Outbound for a source identity that one already supplies.
From an idea to a working connection
Bring the setup you have.
Your devices and connection
Identify the computers, phones, servers or LAN resources involved. A device joins individually; a supported gateway reaches approved equipment behind it. Fibmesh Edge hardware remains a development or pilot option.
Review connection and deployment options →Your audience and traffic
Who starts the connection? Who may use the resource? Do you need a URL, an IP, a private route or an internet exit? Keep application authentication and firewall rules in the plan.
Understand security responsibilities →Your available service
Check the product, native platform, location and address-family support for the proposed deployment. Fibmesh helps you confirm the deployment requirements and arrange setup.
Check availability →Understand pricing and access →Have a specific connection in mind?
Discuss your setup ↗