Hardware matrix

Hardware support should be published with install and recovery evidence.

This pre-launch matrix defines the hardware classes and evidence required before The Gateway claims support.

Primary gateway

Requires fresh-machine install, route/DNS ownership, fallback, rollback, and recovery evidence.

Embedded router

Requires platform constraints, storage/RAM limits, networking behavior, and rollback notes.

Portable node

Requires captive network behavior, bridge path, privacy posture check, and recovery notes.

Appliance candidate

Requires image build, update path, backup/restore, hardware fit, and support boundary.

Relay or bridge

Requires reachability, route policy, fallback behavior, and abuse boundary.

VPS node

Requires provider constraints, firewall behavior, route policy, recovery, and privacy boundary.

Next action

Collect redacted hardware reports before marking support.

Use hardware reports to capture device class, install outcome, route/DNS checks, fallback behavior, recovery path, and remaining risk.