What is finished, and what is not#

Wheelhouse is a working router platform with real gaps, and this page is the list of both. It exists because the alternative — finding out after you have moved a network onto it — is worse for you and worse for us. Everything below is either a claim with the file that proves it, or a gap with the file that admits it. It is kept in step with the repository's own status section in README.md and with the status page on the product site; when one changes, the others change with it.

Built, and exercised#

Two of those numbers can be re-derived rather than believed:

grep -h '^func Test' agent/*_test.go | wc -l    # over 200 Go test functions
cd agent && go test -race ./...                 # they run race-clean in CI
ls ui/src/pages/*.tsx | wc -l                   # a page per nav entry

What has actually been run#

The verification inventory, from the repository's own history — docs/hardware.md.

If you are evaluating this, install it in a VM first. That is the path with the most evidence behind it, and it exercises the same installer, the same units and the same first-boot sequence as the metal.

Not finished, and worth knowing before you buy#

• No bare-metal install has been done, as above. There is also no VM image — no qcow2, no OVA — and images are amd64 UEFI only. The arm64 .deb exists for running the agent off-router against an arm64 router; there is no arm64 image.
• The end-user terms are a placeholder, marked as one in their own first paragraph. Nothing should be sold until real terms replace them — The Wheelhouse licence.
• IPv6 is configurable but not observable. There is no v6 route view and the uplink model has no v6 concept; the Firewall page is v4-first.
• The audit log cannot leave the box and is not tamper-evident. It is complete — every mutating route records who did what from where, fleet writes included (agent/main.go, handleFleetConfigure) — but there is no syslog or SIEM export, and nothing signs it. Root on the box can rewrite it invisibly.
• App images float. All 36 container entries use :latest, so what installs today is not what installed last month. Digest pinning is tooled and not applied.
• There is no support bundle. Diagnostics are four manual API calls — Support.
• Releases are not signed. The pipeline signs checksums the moment a key exists; no key does. A checksum proves the download survived the network, not who built it.
• There are no UI tests. The agent has over two hundred test functions and CI runs them race-clean; ui/ has none, and CI only typechecks and builds it. Testing is not uniform and should not be described as though it were.
• Packet capture is not implemented. POST /api/capture answers 501 and hands back the monitor traffic command to run by hand, rather than reporting a capture that never started.
• UPnP has no answer. No credible published miniupnpd image exists, so the gap stays open and the page says so.

Shipped, but narrower than the name suggests#

The features below exist. Each is smaller than a reader might assume from its name, so the boundary is stated here rather than discovered later.

Commercially, what is not ready#

What this page is for#

Every release is driven in a browser against a live replica router before it is tagged. That is a real bar, and it is not the same bar as a hardware compatibility programme, a signed supply chain or a support contract. Read this page as the difference between the two, then decide.

See also#

• Roadmap — which of the gaps above are planned, marked as not built.
• Release history — what has changed, release by release.
• Reporting a vulnerability — the security gaps, in more detail.
• The Wheelhouse licence — the commercial gaps, in more detail.
• Requirements — what it runs on, and what has been run on it.
• Install in a VM — the path with the most evidence behind it.

Checked against#

README.md · PLAN.md · docs/hardware.md · docs/security.md · docs/apps.md · docs/multi-wan.md · PRICING.md · SUPPORT.md · agent/main.go · ui/src/pages/Qos.tsx