Open Sokuza — launch your local instance

— →

Open app

Opening your local Sokuza…

This page looks for Sokuza running on your own computer. No app data passes through sokuza.ai — we only check which local port answers, then hand you off.

Probing localhost

Looking for a running instance…

Checking ports 24847 – 24852 on sokuza.localhost and 127.0.0.1.

Found

Opening …

Version . Redirecting automatically. Tap here if nothing happens.

Heads-up: *.localhost DNS didn't resolve on this machine, so we fell back to 127.0.0.1. The app still works — the URL just looks different. See install troubleshooting.

Sokuza is bound to (the preferred port 24847 was busy, so it fell through the fallback range).

First visit? The dashboard will ask for a bearer token — run sokuza token in a terminal to reveal it. Subsequent visits unlock silently.

Not detected

Sokuza isn't running on this machine.

We probed the known Sokuza ports on this browser's loopback addresses and got no valid response. Either Sokuza hasn't been installed yet, or it isn't started. Pick the option that matches.

Installed but stopped

Start it in a terminal.

$ sokuza

Then .

Not installed yet

Install it once, then auto-start on login.

$ git clone https://github.com/<owner>/sokuza.git
$ cd sokuza && npm i && npm run build && npm link
$ sokuza init && sokuza install-service

Full guide: sokuza.ai/install.

Install guide

Why can't it be detected?

The browser blocks cross-origin requests to your machine unless Sokuza explicitly allow-lists sokuza.ai. That's a feature, not a bug — it's what keeps other websites from scanning your localhost. If your Sokuza version is older than the one this page expects, pull and rebuild: git pull && npm run build.

Corporate VPNs, firewalls, and aggressive ad blockers sometimes strip the discovery response too. In that case, open Sokuza directly at http://localhost:24847.