Connect a device. Inspect the route.
Start with a privacy-preserving browser preflight. Pair the optional local node agent for exact hardware, then inspect and reserve a compatible private-alpha role from the live coordinator.
No device scanned yet.
Start a private preflight using only signals this browser exposes. Shardwood will check coarse processor and memory hints, site storage quota, WebGPU availability, connection estimates, and this site's own round-trip time.
Read exact hardware. Keep control local.
The installable agent can read GPU model, VRAM, drivers, RAM, and free disk that a web page cannot. It never gives this site your node credential.
Select the button to ask the fixed loopback address 127.0.0.1:17834 whether the Shardwood bridge is running. This check does not read hardware.
Install and start the private-alpha agent
Approved testers receive a signed-hash private-alpha ZIP out of band. Extract it to a local, non-synchronized folder, then verify and install it without Administrator access:
.\Install-ShardwoodPrivateAlpha.ps1 -Action Verify
.\Install-ShardwoodPrivateAlpha.ps1 -Action InstallThen start the bridge for this exact site origin:
.venv\Scripts\shardwood-node.exe bridge --origin https://shardwood.hoodKeep that terminal open. It prints a one-time pairing code that expires after two minutes. Enrollment and coordinator setup are separate private-alpha steps.Choose a compatible private-alpha test.
Listings come only from the paired native agent after the coordinator filters your latest reported capabilities. Nothing below is sample data.
The website cannot read coordinator jobs or hardware credentials directly.
Inspect the route. Reserve only a role your node can actually run.
Capacity colors are job-relative. Health is shown separately from hardware fit.