The official Windows kiosk client for assessments hosted on NEXKAT. It limits navigation, downloads, printing, developer tools, common escape shortcuts, and external sites while an assessment is active.
Before an assessment starts, the app is a normal closable window and also shows a Close Browser control in NEXKAT. After a verified attempt loads, it enters fullscreen kiosk mode, hides the Windows taskbar, blocks the Windows key and common switching shortcuts, and temporarily disables Task Manager for the current Windows user. These controls are restored only after the backend confirms that the attempt was submitted or timed out.
A separate watchdog restores the taskbar and the user's previous Task Manager/Windows-key policy values if the browser exits unexpectedly. The next launch also performs stale-state recovery before opening the platform. Version 1.1.1 also verifies that the Windows keyboard hook is installed before revealing exam content; if the helper cannot start, the attempt stays behind a retry screen instead of continuing without OS lockdown.
On Windows accounts where registry policy writes are restricted, the watchdog uses its active process guard to close Task Manager repeatedly while the exam is running. The Windows-key filter and hidden taskbars remain active in both modes.
Use the latest installer from the repository Releases page. Windows x64 is supported.
npm ci
$env:NEXKAT_PLATFORM_URL = "https://nexkat.me"
$env:NEXKAT_API_URL = "https://api.nexkat.me"
$env:NEXKAT_BROWSER_HANDSHAKE_SECRET = "development-only-secret"
npm startInstitution builds must be provisioned with the same handshake secret configured on the NEXKAT backend. Never commit that value. A public source build without provisioning can browse the platform but cannot open secure-only assessments.
For a distributable build, copy provisioning.example.json to the ignored provisioning.json, set the secret, and run npm run build. Official release automation reads the value from a protected GitHub Actions secret.
This client provides strong application-level Windows lockdown. Windows reserves the secure attention sequence (Ctrl+Alt+Delete), so blocking that sequence itself requires a managed Windows device configured with Assigned Access and Keyboard Filter. See SECURITY.md for responsible disclosure and deployment guidance.
MIT