Product website, documentation, installation guide, readiness checklist, support boundaries, privacy posture checklist, and evidence pages.
Product status
The Gateway is released and available to install.
This page summarizes the current product surface: installation, documentation, support scope, evidence, and limits operators should understand before relying on a gateway.
Start with the installation guide or readiness checklist, then validate route/DNS owners, fallback expectations, recovery access, and intended privacy posture.
Guided setup and operational help are available within explicit operator-approved boundaries. Credentials, traffic ownership, recovery, and final approval stay with the operator.
Keep install notes, route/DNS traces, fallback checks, leak checks, rollback drills, hardware reports, redacted screenshots, and a note for the operational claim each artifact supports.
Public screenshots should show the actual operator surfaces: dashboard, routing policy, DNS, devices, backup, recovery, and validation views. Private hostnames, account names, addresses, keys, and topology details should be replaced with realistic synthetic examples before publication.
The Gateway does not guarantee anonymity by itself and does not make logged-in accounts, browser fingerprints, payments, endpoint compromise, or malicious relays private.
Public materials should stay focused on operator value, product readiness, limits, and evidence. Internal maintenance notes belong in maintainer docs, not on this status page.
The production domain, docs host, install path, rollback path, security policy, evidence package, and known limitations are aligned for the public product.
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
Current public surfaces are live and organized by operator task.
Homepage, documentation map, product status, support boundaries, contact privacy, evidence checklist, and readiness checklist are available now. The visitor-facing story stays focused on product value, proof, and operator boundaries.
The public site uses https://thegateway.pro/ as the single canonical host, and public host routing should keep visitors on that production surface.
Repository materials should keep license, security policy, contribution guide, support policy, issue templates, install docs, and release checklist aligned.
Security checks should continue to report no unresolved high-severity issues before each release update.
Support, appliance, managed operations, and MSP paths need explicit redaction rules, owner assignment, and repeatable proof for each deployment.
Visible proof
The current screenshot set covers the public readiness story.
Shows the operator view behind route ownership, DNS posture, tunnel health, device state, and backup readiness.
Shows how policy attaches to client groups before hardware or appliance support claims are applied to a deployment.
Shows the backup and restore surface that should support rollback evidence before traffic depends on the gateway.