HOKIO / DOWNLOADS
Install Hokio on your device.
Connect a local application using Webhook, Public URL, or Both with the native Hokio preview. Existing installations can continue using the legacy Webhook connector. Your application owns its port; choose that same port in Hokio on your device.
Native Hokio preview
A standalone program for Webhook and URL connections. This preview is distributed separately from the Microsoft Store app; keep an existing embedded connector under its host program's control.
Windows x64 · 0.2.0-alpha.2
Download the Windows installer · Installer SHA-256 checksum
Run the installer for your Windows account. Close and reopen PowerShell or Windows Terminal, then run these commands from any folder:
hokio --version
hokio setup
hokio service install
hokio service start
hokio service statusThe installer adds its separate Programs\HokioNative folder to your user PATH. The installer itself does not register a device or create a service: the commands above complete setup and enable background startup. It does not change the legacy Store or embedded installation. If another installation already provides hokio, setup stops and reports the conflict instead of replacing that command.
Portable download without PATH changes
Download the portable Windows executable · SHA-256 checksum. Save as hokio.exe in a permanent folder and use .\hokio.exe instead of hokio for the setup and service commands above.
This standalone preview is not Store-signed. Follow your organization's software approval policy; do not disable security protections. Windows 7 and 8 are not supported by this package.
Linux 64-bit and 32-bit · 0.2.0-alpha.4
Portable Linux packages work across glibc and musl distributions without requiring a specific glibc or OpenSSL version. The installer automatically selects x64, ARM64, x86 (i686 with SSE2), or ARMv7 hard-float. Install your distribution's ca-certificates package and have curl and sha256sum available. Older i586 and ARMv6 devices are not supported. Review the installer, then run:
curl -fsSL https://hokio.dev/download/install.sh | sh
"$HOME/.local/bin/hokio" setupOn distributions with an available systemd user manager, enable background operation after setup:
"$HOME/.local/bin/hokio" service install
"$HOME/.local/bin/hokio" service start
"$HOME/.local/bin/hokio" service statusThe installer verifies the release checksum and checks that the binary runs before installing it. The main install command now installs native Hokio in ~/.local/bin/hokio. Existing hokio-agent binaries, services, credentials, and assigned links are preserved. A conflicting hokio command or an unsupported system stops installation. The script installs the program; the separate service commands above enable and start its systemd user service. Your user service manager must be available. On Alpine/OpenRC, runit, or another init system, run ~/.local/bin/hokio run under your existing supervisor instead of using the systemd commands. No supervisor or privileged service is installed automatically. It does not change your local application or replace hokio-agent.
One code, setup on your device
Sign in, select your workspace and branch, then generate a code in Connect a device. During setup, paste it when prompted, choose Webhook / Public URL / Both, and enter your application's listening port. For URL or Both, choose an available subdomain. Webhook addresses are assigned automatically.
The preview reserves a Webhook link during registration even in URL-only mode. URL access also requires the URL feature and capacity in your plan. Complete setup, then install and start the background service. You can close the setup terminal once it is running. Windows automatic startup occurs at user sign-in; Linux requires its user service manager. Keep the device and local application running, and check hokio status to confirm the connection. See the complete guide for background startup, name conflicts, port changes, and plan restrictions.
Legacy Webhook connector
These packages remain available for existing workflows and new Webhook-only connections. They use hokio-agent or the existing Store app; they do not provide the native preview's URL setup. Do not replace an embedded installation independently of its host program.
Install Hokio on Windows
Install Hokio from its Microsoft Store page (opens in a new tab). The Store checks whether its package can be installed on your Windows version and device. We do not offer a Windows 7 or 8 installer on this page.
After installation, open Hokio and check that its connection screen appears. If the Store reports that your system is unsupported, do not use an unrelated installer; contact your workspace owner for supported options.
Install the legacy Webhook connector on Linux
Use a Linux system with a supported release and architecture. The installer checks the environment and release checksum; it reports an error if no suitable package is available. Review the legacy installer script before running it if your environment requires that.
curl -fsSL https://hokio.dev/static/downloads/install-legacy.sh | shVerify that the command is installed:
hokio-agent --helpAn installer error means the device is not ready to connect. Save the exact error and contact your workspace owner; do not bypass package verification.
Connect your device with a one-time code
Start your own local application first and note the port on which it listens. In your workspace, an authorized member creates a one-time device code. Enter that code in the Windows application, or on Linux run:
hokio-agent login --panel-url https://hokio.dev --port 8000 --connectReplace 8000 with your application's actual local port. Enter the code only when prompted; do not put it in a shared command or screenshot. The connector reports its assigned webhook URL after successful registration. Check the connection using hokio-agent status on Linux or the Windows connection screen. The local application and connector must both remain running to receive requests.
The panel cannot start your application or change its local port. For application connection steps and a public request test, follow the webhook quick start.
Installation troubleshooting
- The device code fails
- Ask the workspace owner for a new code. Codes expire and can only be redeemed once.
- The connector cannot reach the local application
- Verify that the application is running on this device and that the chosen port matches its listener. Try its localhost address before testing the public URL.
- The installation fails or your OS is unsupported
- Keep the error message and installation logs, then contact your workspace owner. An unsupported system is not fixed by changing the panel port.
- The device is offline
- Its assigned address remains reserved, but new inbound requests cannot reach the application while the connector or device is offline.