Solutions for the way you work
Find the scenario that fits your work: developing software, connecting teams and sites, or supporting customer installations. Explore the deployment before choosing a product.
01 / Find your audience
Choose the closest starting point. Each journey explains the connection, the product fit and a useful first deployment.
The software you build. The infrastructure you choose to run.
Reach a private build host, share an app preview or connect to an external API.
Keep services on your hardware and choose an audience for each one.
Connect workloads across providers or assess public address delivery to your infrastructure.
People and resources in different places, with a clear reason to connect.
Give colleagues and contractors access to project tools, storage and workstations.
Plan access for approved people, office applications and cloud resources.
Reach selected local resources through a supported gateway at the site.
A connection to install, a customer to support and an owner for the handover.
Deliver a customer connection with agreed installation, ownership and handover.
Give technicians a customer-approved path to installed equipment and software.
Reach existing appliances directly where supported, or through a nearby gateway.
02 / Deployment stories
Two anonymous customer examples and an Edge pilot show different jobs. The scope of each connection matters.
Anonymous customer example
Public IPs · Full tunnel
A restaurant-chain deployment used Public IPs with full tunnel for shared billing access across locations.
The example describes public address delivery and internet routing; it does not establish a private branch mesh.
Read the billing example →
Anonymous customer example
Public IPs · Full tunnel
An anonymous deployment used Public IPs with full tunnel to reach a customer-hosted ERP service.
The application stayed on the customer’s infrastructure. The connection did not replace its application accounts or operating responsibilities.
Read the ERP example →
Customer proof of concept
Gateway delivery · Edge pilot
The original customer POC used a preconfigured Fibmesh Edge device and one configured LAN target. The equipment retained its local address and router.
Multiple targets with distinct protocol and port mappings are a later gateway design, separate from that single-target POC. Edge hardware remains development/pilot.
Explore gateway delivery →03 / Start here
Bring a concrete job to the first conversation. We can help identify the product and supported deployment to evaluate.
Choose one device, application, service or site. Note its platform, address and protocol.
A colleague, client, technician or external system? Decide who should reach it and whether the path should be private or public.
Open the application, complete the job, check the intended permissions and verify the reply path.
Start with the connection you need to make.
Plan a first deployment →