Fibmesh PublishAvailable
Give your web app or API a public HTTPS address. Keep it on your infrastructure, with application login under your control.
studio-portal.publish.fibmesh.exampleOne connection. Separate addresses.
A portal, an API and a preview can share a connector. Each gets its own hostname and an explicit destination.
https://studio-portal.publish.fibmesh.exampleA browser or API client starts here. No Fibmesh client needed.127.0.0.1:3000Application checks accessCustomer portal: the connector on the app host forwards to 127.0.0.1:3000. Replies follow the connection back through Fibmesh.
Share a web address for the portal you already run. Customers sign in with the application’s account; they do not need a Fibmesh client.
studio-portal.publish.fibmesh.example127.0.0.1:3000192.168.1.20:3000Give an integration a public HTTP endpoint. Validate API credentials and webhook signatures in your application before accepting the request.
studio-api.publish.fibmesh.example127.0.0.1:8080192.168.1.30:8080Share a selected preview with the people reviewing it. Use test data, protect access in the app and pause or remove the publication when the review ends.
studio-preview.publish.fibmesh.example127.0.0.1:5173192.168.1.40:80Illustrative addresses, not live services. .example is reserved for examples; the production suffix is not final. The connector must establish its WireGuard tunnel before visitors use the address.
Each publication pairs one hostname with one selected HTTP application and port. Pause one without changing its neighbours, or retarget it when the app moves. Verify the new destination before sharing.
For your visitorsA browser or API client.
For your applicationA public web URL of its own.
For your siteAn outward connector tunnel.
Keep the app where it belongs
Keep the application on the infrastructure you maintain. Place the connector beside the app, or on its LAN with a path to the selected service.
Explore apps & devices →Run the background connector on a supported server or computer. It forwards the chosen requests to an app on that machine, including localhost.
localhost:3000Localhost refers to the connector’s own machine.
Use a supported LAN connector to reach a selected web service on another server or device. The target keeps its existing local address and software.
192.168.1.20:3000Confirm connector support during setup. Edge hardware remains a development and pilot option.
Useful things, within reach
A familiar web address for an application you maintain. Keep its accounts, data and hosting under your control.
Self-hosted portals ↗A public endpoint for an API or webhook sender. Let the application validate tokens, signatures and incoming requests.
APIs & webhooks ↗A review link for a selected development app. Protect it in the application and retire the publication after the review.
Review environments ↗Public reach. Deliberate scope.
A public URL makes the app reachable. Its login, permissions, API credentials and webhook checks decide what a visitor can do. Fibmesh-managed visitor access is a planned extension.
Visitor HTTPS terminates at the Fibmesh gateway, which processes the request. WireGuard protects the connector tunnel. Use appropriate HTTP/HTTPS protection between the connector and the app, especially across a LAN.
Publish routes a selected HTTP app by hostname; each app does not need a dedicated public IPv4. Use Networks for private resource access, or assess Public IPs for address-level reachability and other supported protocols.
Compare connection options →The connector initiates its tunnel outward, so the origin does not need a dedicated public address or an inbound router port-forward. Your internet path must permit the required WireGuard UDP traffic. CGNAT can work when that connection can be established and maintained; restrictive networks need testing.
The core model uses a Fibmesh-managed subdomain for each publication. Custom domains are a planned extension with separate ownership, DNS and certificate requirements.
Explore domains & access →The app, its host, the background connector and their internet path must remain available. Closing an administrative terminal does not stop a persistent connector, but suspending the host can interrupt it. Publish does not supply application hosting or backups, and leaves the host’s ordinary outgoing route in place.
Confirm application and connector compatibility during setup. WebSockets, SSE and device web interfaces need application-specific checks. Raw TCP, UDP and local discovery are outside the web publishing model. Video streams and native clients can need other protocols. Separately marked proposals remain outside the released scope; CLI commands are proposed syntax.
Your first publication
Tell us what runs, where it lives and who needs to reach it. We’ll help confirm the right setup.