Fibmesh Publish / Use cases
A portal on an office server. A preview on a workstation. An API on your own compute. Publish gives an HTTP application a public entry point where it already runs.
Explore six deployments Use-case guide · Confirm platform and deployment support during assisted setup.Publish is available with assisted setup. Confirm supported platforms and deployment requirements. Separately marked proposals remain outside the released scope.
Illustrative deployments, not completed customer installations. Every .example address below is non-live; application authentication still applies.
01 / Business applications
A business runs a customer portal beside its inventory system on an office server. Customers need the portal without access to the rest of the office network.
The publication routes its public hostname to the portal’s web address and port through the server connector. The app owns customer accounts and data permissions. Its database stays an internal dependency with no publishing rule.
Choose a supported always-on host. Plan the public base URL, dependable app login, backups and office upload capacity. Publish supplies reachability; you still host the app and store its data.
https://studio-portal.publish.fibmesh.examplePublic HTTPS addressAn application dependency, with no publishing rule.
02 / Integrations
A developer tests an integration, or a team runs an API on its own server. An external system calls the HTTPS endpoint without joining a private network.
https://studio-hooks.publish.fibmesh.examplePublic HTTPS address03 / Client review
A studio gives a client a browser address for a preview running on its workstation. Keep test data in that environment and use the application’s access controls for the review.
https://studio-preview.publish.fibmesh.examplePublic HTTPS address04 / Self-hosted services
A document portal, reporting tool or collaborative web app can live on a home server, dedicated machine or cloud VM. The publication’s hostname is separate from the current hosting provider.
https://team-docs.publish.fibmesh.examplePublic HTTPS addressBring up the application on the new infrastructure.
Verify the new target before changing the publication.
Manage data, databases and active sessions separately. A hostname change does not move them or guarantee uninterrupted migration.
Plan sustained bandwidth, resource limits, application updates and a realistic availability target. Private file shares and backup protocols may be better served by Networks.
05 / Edge and local equipment
A software vendor needs browser access to an application at a customer site. Its server cannot run a connector; a Fibmesh Edge connector on the LAN can reach it.
https://branch-console.publish.fibmesh.examplePublic HTTPS addressGet customer approval, retain application authentication and choose a stable target address and port. Use LAN HTTPS where required: WireGuard protects the path to Edge, not a later plaintext LAN hop.
A Windows desktop ERP, NVR stream or proprietary native client needs protocol assessment. A public web link is not a universal remote-access client.
Other site applications can have separate links. Ordinary local and outgoing traffic keeps using the existing network.
06 / Compute and specialist workloads
A team runs an inference API or processing service on its own machine. Publish supplies the intended HTTP entry point while the workload stays with that compute.
https://lab-api.publish.fibmesh.examplePublic HTTPS addressCheck streaming response buffering and timeout settings, concurrent connections and request sizes.
Large jobs may need an application-level job API instead of one very long request. Plan processing duration.
Enforce application quotas and cost controls before accepting expensive work.
Raw model-serving protocols, GPU scheduling and job queues remain outside Publish’s role.
Choose the access model
The place an application runs does not decide the product. The access your people, devices or services need does.
People or API clients need to reach a web application.
Colleagues and devices should join a private network.
Clients need an address or supported non-HTTP service delivery.
An application needs a selected source IP for outgoing connections.
Next / Getting started
Confirm the audience, connector and target. Then test HTTPS, application authentication and a real visitor task before sharing the address.