Try the model
See what a publication connects.
Choose an app and where its connector runs. This local example shows the public address, the app’s private address and the checks that matter. It does not provision a service.
- Application target
http://127.0.0.1:3000- Audience and authentication
- Customers sign in to the portal using its own login.
- What to verify
- Login, customer permissions, uploads and logout.
The target address is read from the selected connector. An Edge connector uses a reachable LAN address instead of another machine’s localhost. The Fibmesh subdomain above is illustrative; .example is not live and the production suffix is not final.
Prepare
Know the target before you create the link.
The application
Record its HTTP or HTTPS address and port, owner and required login. Check that it responds from the selected connector. Identify WebSockets, redirects, uploads and any non-HTTP dependencies.
The connector
Choose the application host or an Edge connector with a route to the LAN service. Confirm supported software, installation permissions, power and an internet connection that permits WireGuard traffic.
The audience
Identify the people or systems that need to connect. The app supplies authentication. Protected browser access and managed machine credentials are separate planned extensions.
The operating owner
Name the person responsible for the publication, the application and the host. Decide who can change the target, respond to a fault or remove access.
Assisted setup
Select the app. Connect it. Verify the public path.
- Select the workspace and connector.
Enroll a supported connector, then confirm that it belongs to the workspace you selected and has established its outbound WireGuard tunnel to Fibmesh.
- Select the application.
Enter the protocol, address and port from the connector’s point of view. Check the target locally before troubleshooting public routing.
- Choose the address and confirm application access.
Use a managed hostname for the core workflow. Custom-domain attachment follows its own ownership and certificate checks when supported. Public reachability must be an explicit choice. Check the app’s own login or API authentication; Fibmesh-managed visitor gates remain a planned extension.
- Review and activate.
Review the exact target and intended exposure. The gateway and connector apply the authorised configuration; certificate and health status determine whether the public endpoint is ready.
- Verify as the real visitor.
Use a browser or API client outside the app’s network. Complete a real application task and test a request that should be denied.
Arrange setup with Fibmesh. This guide explains the checks; confirm supported software and the operator procedure for your deployment. The proposed CLI examples are not installation instructions.
Review the proposed CLI workflow →Your first deployment
Test the application, not just the homepage.
Check login and logout, links, redirects, file transfers and live updates. For an API, check authentication, error responses and webhook signatures. Confirm that another app on the same host does not acquire access through this publication.
Disconnect the connector and inspect the public failure response. Restore it and verify recovery. Pause the publication, check new requests and inspect the handling of existing sessions. Record the supported version and observed result before expanding the deployment.
Keep an independent local administration path to the host or Edge device. Do not depend on the publication you are testing to recover its own connector.
Your next step
Bring a useful first application.
Available · Assisted setup
Tell us what you want to put online.
Tell us about the application, where it runs and who needs access. We’ll help you confirm the connector, hostname and deployment requirements. Do not include credentials, private keys or customer data.
Request Publish setupOpens your email application. Your request is sent only when you send the email.
Deployment scope, timing and commercial terms are agreed with Fibmesh before setup.