Users open the public app address after they are allowed into the app. BusinessProxy checks the session, forwards only that app traffic through the connector, and keeps the internal hostname and private IP out of the user-facing URL.
App addresses Guided onboarding
Public HTTPS addresses for internal web apps
A public app address is the safe external URL users open for a selected internal app. The real internal address stays inside your network and is reached only by the assigned connector after BusinessProxy creates an approved app session.
App Gateway is enabled with guided onboarding. We review the target app, connector reachability, public app address behavior, diagnostics and revoke flow before turning on regular access.
External entry point
A stable URL for the app, not a route to the network
User experience
What the user experiences
- They sign in to BusinessProxy and see only apps assigned to them.
- They open one app through its public HTTPS address.
- The app session is scoped to that app and has a limited lifetime.
- An administrator can revoke the session without changing the internal app.
Why teams use public app addresses
- External users do not receive a device-wide VPN or private network route.
- Internal hostnames and private IPs stay behind the connector.
- Access is granted per app, per user or group, and can be revoked centrally.
- If the app or connector is unavailable, access closes instead of falling back to a broader route.
Docs
Where technical setup lives
Rewrite behavior, internal TLS validation, connector readiness and sanitized error handling belong in the setup docs. A public app address gives users a stable app entry point while internal topology stays behind the connector.