Trust model, route ownership, DNS ownership, fallback policy, support boundaries, privacy posture limits, and install readiness questions.
Launch status
Pre-launch, useful to review, not yet a broad self-service install.
This page separates what operators can review now from the release gates that still need public evidence, production endpoints, and repeatable recovery proof.
Request an install readiness review with topology, route/DNS owners, fallback expectations, recovery access, and intended privacy posture.
Broad self-service install, hardware support claims, appliance builds, managed operations, MSP workflows, and production conversion endpoints.
Fresh-machine install transcript, route/DNS traces, fallback checks, leak checks, rollback drill, hardware matrix, screenshots, and redacted support bundle example.
The Gateway does not guarantee anonymity by itself and does not make logged-in accounts, browser fingerprints, payments, endpoint compromise, or malicious relays private.
Guided help should be advisory or bounded by an explicit change window. Credentials, traffic ownership, recovery, and final approval stay with the operator.
Status by surface
Public copy can be visible before every operational surface is ready.
Homepage, documentation map, launch status, support boundaries, contact privacy, evidence checklist, and readiness intake can be reviewed now.
Repository launch should wait for license, security policy, contribution guide, support policy, issue templates, install gates, and release checklist.
Support, appliance, managed operations, and MSP paths should wait for real endpoints, redaction rules, owner assignment, and repeatable proof.