Confirm deployment mode, admin access, recovery path, DNS state, route state, firewall state, and backup location.
Install guide
The self-service install path waits for fresh-machine evidence.
This pre-launch guide defines the install flow The Gateway needs before broad public release.
Map interfaces, prepare host OS, start local service, configure device groups, DNS policy, route policy, and fallback behavior.
Review route ownership, DNS ownership, direct escape paths, fallback behavior, and rollback path before apply.
Apply only after rollback is known and operator approval is explicit.
Check local admin access, DNS resolver behavior, routes, fallback, leak behavior, and privacy posture.
Install evidence should stay redacted, reproducible, and tied to a specific hardware class and route/DNS state.
Install notes should describe rollback, recovery access, operator approval, and unsupported assumptions before anyone treats the path as self-service.
Public copy stays focused on operator value, product readiness, support boundaries, privacy limits, and evidence.
Published install assets should avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions.
Save install transcript, evidence links, known limitations, and remaining risks.
Install evidence
Self-service install needs screenshots for configuration, validation, and rollback.
Shows the client groups that should be configured before route and DNS policy apply.
Shows the route profile and fallback behavior that should be reviewed before apply.
Shows the dashboard evidence that should accompany install transcripts and remaining risks.