Demo video, screenshots, supported hardware matrix, install transcript, public test summary, production-site verification, recovery drill, privacy posture check, and the first operator report.
Evidence checklist
Public proof keeps privacy claims honest.
The Gateway documents evidence for install behavior, privacy posture, recovery, and operator workflows so visitors can judge the system before they trust it.
When evidence includes logs, screenshots, or support bundles, start with the redaction guide before you attach anything.
No automatic anonymity guarantees, no hidden traffic inspection, no unproven install claims, and no unsupported hardware promises.
Evidence ledger
Every launch claim should map to a proof artifact and a remaining risk.
Needs fresh-machine transcript, hardware profile, dependency list, setup duration, known failure points, and rollback note.
Needs before/after route table, intended egress, fallback trigger, blocked-path proof, and operator approval note.
Needs resolver map, upstream list, forced-DNS proof, bypass handling, per-device sample, and redacted query evidence.
Needs UI screenshots that show the operator surface behind the claim: dashboard, routing policy, DNS, devices, backup, recovery, or validation views. Replace private hostnames, account names, addresses, keys, and topology details with realistic synthetic examples before publication.
Needs a short note explaining what was redacted, what synthetic values replaced it, and which operational claim the screenshot supports.
Needs route/DNS/leak checks, browser and account caveats, transport assumptions, and explicit non-anonymity boundary.
Needs a public security summary, known limitations, disclosure path, and any relevant audit or review result before the claim is treated as publishable.
Needs rollback command, backup restore evidence, recovery access proof, stop condition, and known-good timestamp.
Needs redaction guide, bounded access rule, retention expectation, revocation path, and proof that credentials stay with the operator.
Evidence hygiene
Publish enough proof to be useful without leaking operator context.
Redacted screenshots, summaries, sanitized command output, hardware class, version, result, limitation, and the claim each artifact supports.
Private keys, tokens, customer names, account identifiers, private hostnames, full traffic captures, private IP maps, and unredacted topology.
Unsupported hardware, untested rollback paths, unknown relay trust, incomplete leak checks, and any result that has not been reproduced.
Screenshot set
Use visual proof only when it supports a concrete operator claim.
Shows route, DNS, tunnel, device, and backup state together with realistic synthetic values.
Shows named policy intent, fallback behavior, and device scope without private topology.
Shows resolver policy, upstream choices, and filtering posture with synthetic domains.