# Hardware Matrix

The Gateway hardware support should be published only with evidence. This matrix is a release gate template until tested devices are documented.

## Status Levels

- `supported` - tested install, route/DNS checks, fallback checks, recovery path, and known limitations documented.
- `partial` - usable with documented limitations or missing evidence.
- `untested` - plausible target, no public install evidence yet.
- `blocked` - known blocker prevents safe use.

## Hardware Classes

| Class | Status | Evidence Required |
| --- | --- | --- |
| Primary gateway | untested | Fresh-machine install, route/DNS ownership, fallback, rollback, recovery. |
| Embedded router | untested | Platform constraints, storage/RAM limits, networking behavior, rollback path. |
| Portable node | untested | Captive network behavior, bridge path, privacy posture check, recovery. |
| Appliance candidate | untested | Image build, update path, backup/restore, hardware fit, support boundary. |
| Relay or bridge | untested | Network reachability, route policy, fallback behavior, abuse boundary. |
| VPS node | untested | Provider constraints, firewall, route policy, recovery, privacy boundary. |

## Report Requirements

Hardware reports should include:

- Device class.
- Vendor/model.
- CPU, RAM, storage, and network interfaces.
- Operating system.
- Install outcome.
- Route ownership check.
- DNS ownership check.
- Fallback behavior.
- Recovery or rollback path.
- Privacy posture notes.
- Redacted evidence.

Do not include private hostnames, private IP maps, account identifiers, customer names, keys, tokens, or unredacted topology.