No inbound port

Both computers open an outbound HTTPS/WSS connection to the relay. Neither machine accepts an inbound connection, so there is nothing to forward on your router and no inbound firewall rule to add. The relay queues messages between the two and never holds a model.

Pairing

1. On the computer doing the asking, press Add benchmark computer for a one-time code.
2. Enter that code on the other PC. It sends its signed-in account email and public-key fingerprint through the relay.
3. The host sees the email and the full key fingerprint, and approves or rejects it. A machine you have not approved cannot be asked to do anything.
4. Request a DirectX probe, or a benchmark of the model selected on that client. The client confirms before anything runs.
5. Read the result.

What comes back is evidence, not a headline

Each completed run returns: model id and SHA-256, tokens per second and total ms, the prefill/decode split, peak RAM and VRAM, GPU adapter and driver version, and whether a fallback path was used.

That last field is the one that matters. If the GPU path was not actually used, the run says so instead of quietly reporting a CPU number as a GPU result.

What never crosses the network

Model weights stay on the machine that runs them — never uploaded, never relayed. Prompts and answers stay local too; a remote run measures speed, not text.

Availability

Remote benchmarking is part of Pro. The five-day trial covers local benchmarks, the dashboard and both native engines; buying credits once adds remote runs and keeps them.

Full details: https://lizard-llm.qendryx.com/remote.html

Question: which two machines are you comparing, and how far apart did they land?