- Deployment mode, interfaces, upstream router constraints, and recovery access.
- Hardware fit for primary, embedded, portable, or appliance-style deployment.
- DNS, routing, fallback, privacy posture, and evidence expectations.
- Safe-mode recovery needs for DNS, routing, firewall, and admin lockout.
Install readiness
Request an early install readiness review.
The Gateway is preparing the public open-core install path. Use this review to map hardware, route and DNS ownership, recovery access, privacy posture, and fallback expectations before relying on a gateway.
- Choose deployment mode and map interfaces.
- Bootstrap daemon and local UI.
- Create device group, DNS policy, route profile, and fallback behavior.
- Validate connectivity, DNS trace, route trace, fallback state, and leak checks.
- The repository install guide will become the self-service path after fresh-machine verification.
- Until then, early installs should document backup, rollback, ownership, and support bundle expectations.
- Keep route ownership, DNS ownership, fallback behavior, and recovery expectations explicit before anyone relies on the gateway.
Before you request review
Make route ownership, DNS ownership, fallback policy, and recovery proof explicit.
- Name the current route owner, DNS owner, fallback owner, and final apply approver.
- State whether the review is advisory only or preparing for a bounded live install window.
- Document the current route, DNS, fallback, and policy state before the first install attempt.
- Confirm console, SSH, or local recovery access before changing DNS, routes, firewall state, or remote access.
- Keep a known-good rollback target or timestamp for policy, resolver, and transport state.
- Stop the install window if recovery access or rollback proof is missing.
- Describe the intended privacy posture and what evidence will verify it after install.
- If screenshots are part of the evidence package, redact real values into realistic synthetic values and note which operational claim each image supports.
- Make fallback behavior visible instead of assuming tunnel or bridge safety.
- Review support and export boundaries before sharing diagnostics or granting remote access.
Cross-check the privacy posture checklist, rollback and recovery guide, support boundaries, and trust and security model before requesting early install review.
Review surfaces
Prepare evidence from the operator views that will change during install.
Shows route chains, fallback mode, and device scope before the install window changes traffic behavior.
Shows resolver policy, filtering posture, and bypass handling that should be checked after install.
Shows which clients and groups are in scope so review notes can avoid accidental whole-network assumptions.