Keep thegateway.pro as the production domain, update canonical URLs if the domain changes, and serve the static site behind production TLS. Public host routing should keep visitors on the canonical site.
Launch dependency roadmap
What must be wired before broad public launch.
The static website is wired. These are the external accounts, URLs, and proof artifacts that turn the launch pages into production infrastructure.
Publish repo, license, security model, contribution guide, support policy, install guide, hardware matrix, releases, release checklist, and repository readiness gates.
Keep public launch copy focused on operator value, product readiness, privacy limits, support boundaries, and evidence while the launch roadmap stays visible to operators.
Keep public launch copy focused on operator value, product readiness, privacy limits, support boundaries, and evidence.
Published assets should avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions.
Replace mailto templates with real sponsor, support, appliance waitlist, MSP pilot, and evidence intake forms.
Add demo video, screenshots, install transcript, test summary, recovery drill, and first runbook execution report.
Make hello@thegateway.pro real or replace it, then publish privacy/contact handling notes for intake messages.
Add privacy-respecting analytics only after deciding what launch signals matter and what data should not be collected.
Launch gate order
Wire public systems before sending broad traffic.
Make the domain, email address, sponsor path, support intake, appliance waitlist, MSP pilot, and security reporting path real.
Publish license, security policy, contribution guide, support policy, issue templates, release checklist, and install gates.
Attach demo screenshots, install transcript, route/DNS checks, fallback checks, recovery drill, and a redacted support bundle example.
Confirm support boundaries, analytics privacy, data retention, rollback ownership, and public maintenance funding path.
Dependency proof
External launch systems should point to concrete operator evidence.
Supports demo, screenshot, and public test summary dependencies.
Supports install docs, route/DNS verification, and contribution examples.
Supports support, appliance, MSP, and rollback dependencies before broad traffic.