Signed image, preconfigured mini PC, portable gateway, or small-office appliance.
Appliance waitlist
Request a signed build or preconfigured gateway.
The appliance path exists for operators who want the privacy overlay outcome without building the whole stack from scratch. Hardware can be prepared, but route ownership, DNS ownership, fallback policy, recovery access, and final approvals still need named owners.
Home, lab, travel, office, MSP site, or bridge relay deployment with current route and DNS constraints.
Choose self-install, guided setup, backup/restore help, or a managed update path without transferring traffic ownership by default.
Early appliance requests are matched against hardware constraints, policy goals, fallback behavior, recovery expectations, and support boundaries before a build is promised.
- Name the current route owner, DNS owner, fallback owner, and final approver for the site.
- State whether the appliance will replace the current router, sit beside it, or cover only selected segments.
- Document the policy source of truth if route, DNS, or fallback settings are managed elsewhere today.
- Describe console, SSH, or local recovery access available if the appliance path fails.
- Record the current rollback method for DNS, routing, firewall, and uplink changes.
- Keep fallback behavior explicit so a failed tunnel or relay does not silently change the privacy posture.
- State whether remote access is allowed, who can grant it, and how it is revoked.
- Share only redacted diagnostics needed for fit review, install help, or recovery review.
- Set support and export boundaries before asking for preconfiguration or guided changes.