Publish an application or API

Put an application within reach.

A customer portal, webhook receiver or review environment can share the same publishing model. Choose the origin and audience that fit your application.

fibmeshPublishIllustrative product model

One application

The client’s review application

  1. Reviewer
  2. Managed Publish link
  3. HTTP preview
Target
Selected enrolled server
Listener
127.0.0.1:3000 · example HTTP app
Other services
Database and administration outside this rule

A public review does not grant private workspace membership.

Example configuration, not a connected account or release confirmation.

Conceptual scenario

Publish / Available

The app stays with its host. Its audience gets a URL.

The Publish model connects selected HTTP applications to public HTTPS hostnames through WireGuard. A host connector reaches localhost; an Edge connector reaches an approved LAN service. Several apps can have separate links over one connector.

A business portal can keep its application login. An API can validate machine credentials or webhook signatures. A review environment can use a separate publication that is retired when the work is complete. Publish is available with assisted setup. Contact Fibmesh to confirm the connector, application and location requirements.

Explore the six Publish deployment scenarios →

Plan the connection

Start with the service, its owner and its audience.

Record where the application runs, which connector can reach it, its protocol and port, and who should use it. Check the complete application, including login, redirects, uploads and live updates. Native protocols outside HTTP require a separate delivery decision.

Choose a host or Edge deployment →Prepare a first evaluation →