hokio.

HOKIO / PRODUCT GUIDE

Two ways into your local app.

Hokio gives the internet two ways into an app running on your own device. A Webhook link receives events from another service; a URL link gives a browser or HTTP client a public address for a local web app. Each has its own connection and policy.

Choose the right link: Webhook or URL

Webhook
An external sender posts an event to your assigned HTTPS Webhook address. Hokio checks the link's methods, paths, source rules and limits, then forwards it through the relay and outbound device connection to the local target selected on the device. Follow the Webhook quick start.
URL
A browser or HTTP client requests your assigned HTTPS URL. The gateway and relay pass supported HTTP traffic through the outbound device connection to your local web application. Your application controls its own login and sessions. Read the local URL guide.

Webhook delivery path: sender to local app

  1. Event senderCalls the assigned HTTPS Webhook address.
  2. Hokio gatewayApplies the link policy and forwards the request.
  3. RelayFinds the connected device; an offline device receives no delayed replay.
  4. Hokio on your deviceUses its outbound connection and the local target selected there.
  5. Your applicationHandles the event and returns a response.

Browser URL path: request to local web app

  1. Browser or HTTP clientOpens the assigned HTTPS URL.
  2. Hokio gatewayRoutes the public hostname to the URL relay.
  3. URL relayForwards supported HTTP traffic while the device is connected.
  4. Hokio on your deviceConnects outward to the local target selected there.
  5. Your web applicationControls login and responds to the request.

When a request cannot reach your local app

The public address remains assigned while its resource remains active. Use the request ID and the device's reported state to identify the recorded stage; a missing activity record does not prove where a request stopped.

Device offline
Restore the device's outbound Hokio connection, then ask the sender to retry. Requests received while it was offline are not queued for later replay.
Local target unavailable
The device may still be connected. Start or repair the local application on that device and confirm the target selected there matches its actual listener.
Policy denial or rate limit
Review the link's effective methods, paths, source rules and limits. A pending policy change is not effective until its delivery is acknowledged.
Application response
A successful connection does not guarantee that the application accepts or authenticates the request. Check the application's own logs and access rules.

Continue with Hokio.

Webhook quick start →

Local URL guide →

Request workspace access →