Production domain, TLS, canonical URLs, sitemap, robots rules, favicon, Open Graph image, and short share preview verified before broad release.
Production checklist
Go live only when the public story matches the operator reality.
This checklist keeps the launch honest: open core first, privacy claims bounded, conversion paths real, and proof artifacts available before broad distribution.
The canonical public site stays on https://thegateway.pro/. Before broad traffic increases, confirm that public host routing, redirects, canonical metadata, and support paths all point visitors to the same production surface.
Release checks should confirm alternate hosts resolve back to the production site so visitors only see one public surface.
Public product copy stays focused on operator value, product readiness, support boundaries, privacy limits, and evidence before launch.
Published assets should avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions.
Security checks report no unresolved high-severity issues before broad release.
Repository, license, security notes, support scope, contribution guide, install guide, release artifact, hardware matrix, issue templates, release checklist, and repository readiness gates published.
Install transcript, screenshots, demo clip, route/DNS evidence, leak check, fallback drill, backup restore, and redacted support bundle example linked.
Published screenshots use realistic synthetic values and note the claim each image supports.
Anonymity claims stay qualified, credential handling is explicit, remote access requires approval, and intake retention is documented.
Sponsor, guided setup, appliance waitlist, MSP pilot, and evidence submission flows reach real inboxes or forms.
First runbook, support boundaries, launch metrics, issue triage, changelog cadence, and public roadmap review are ready.
Go / no-go gates
Use concrete blockers instead of launch optimism.
Domain, email, repository, license, support policy, install evidence, rollback evidence, privacy boundary, and contact paths are all live and checked.
Any placeholder endpoint, unsupported hardware claim, missing rollback path, unclear credential custody, or unverified privacy claim blocks broad launch.
Partial evidence, pilot-only hardware, incomplete analytics privacy, or new managed-service claims should stay gated until reviewed.
Proof assets
Do not open broad traffic until the visual evidence matches the claim set.
Supports claims about route, DNS, tunnel, device, backup, and operator posture visibility.
Supports route ownership, fallback, and per-group policy claims before release promotion.
Supports backup, restore, and rollback claims that should be reproducible before launch.
Launch roles
Each production surface needs a named owner before it can receive traffic.
Maintains canonical URLs, sitemap, public copy, noindex gates, accessibility checks, and visual smoke tests.
Maintains license, security policy, contribution rules, issue templates, change summaries, and install support boundaries.
Publishes redacted proof artifacts, links claims to evidence, and marks uncertain or unreproduced results clearly.
Confirms intake privacy, redaction rules, escalation path, remote-access approvals, retention expectations, and stop conditions.