Back to The Gateway

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.

Domain and hosting

Point thegateway.pro, update canonical URLs if the domain changes, and deploy the static site behind production TLS.

Conversion endpoints

Replace mailto templates with real sponsor, support, appliance waitlist, MSP pilot, and evidence intake forms.

Proof artifacts

Add demo video, screenshots, install transcript, test summary, recovery drill, and first runbook execution report.

Launch gate order

Wire public systems before sending broad traffic.

1. Contact surface

Make the domain, email address, sponsor path, support intake, appliance waitlist, MSP pilot, and security reporting path real.

2. Repository surface

Publish license, security policy, contribution guide, support policy, issue templates, release checklist, and install gates.

3. Evidence surface

Attach demo screenshots, install transcript, route/DNS checks, fallback checks, recovery drill, and a redacted support bundle example.

4. Operations surface

Confirm support boundaries, analytics privacy, data retention, rollback ownership, and public maintenance funding path.

Next action

Replace temporary endpoints with production systems.

Start with domain, email, public repo, sponsor page, support intake, and evidence links.