HOKIO / PRODUCT GUIDE
Know each security boundary.
Hokio webhook security in brief: an HTTPS entry point, an outbound device connection with no inbound ports, and link policies you control. Your local application retains responsibility for user authentication and its own data.
HTTPS entry versus application authentication
The public entry point uses HTTPS. The device connects outward to Hokio rather than requiring an inbound port on the device. HTTPS protects the connection to Hokio; it does not authenticate a Webhook sender or a person opening your local app. Keep authentication and authorization in your application.
Workspace ownership and webhook link policies
Signed-in Account members see resources in their selected workspace according to their permissions. A Webhook can restrict source IP/CIDR ranges, HTTP methods, paths, request rate, body size and timeout. Review a link's effective settings before relying on a rule; URL transport limits are shown separately in its detail.
Device and application boundary
The device selects its local application target and establishes the outbound connection. The panel shows reported connection and target information; it cannot change the application's listening port. An offline device cannot receive a request, and Hokio does not replay it later automatically.
Investigate an incident with request IDs
Request activity shows recorded status, outcome and request ID without displaying bodies, authorization headers, cookies or tokens. A missing record does not prove whether a request expired or never reached Hokio. If you have a workspace, open a support case with the request ID and affected link; do not include secrets or request payloads. If you cannot sign in, contact the Hokio team.
Service availability and traffic limits follow the terms assigned to the workspace.