Launch roadmap

Tester intake now. Retail launch later.

The site is live enough to collect useful tester requests. The next work is controlled testing, workflow hardening, and then public download/licensing infrastructure.

Request Tester Access Review Workflow

Milestones

Keep the public promise aligned with the actual product state.

These milestones are intentionally conservative. They let the website be useful now without implying that payment, account, license activation, or production download systems are already live.

Active

Controlled tester intake

Collect useful tester requests through Tally and manually select creators who can validate real music-video workflows.

Pre-release tester build

Prepare controlled build distribution, setup notes, feedback channels, and known-issue tracking for selected testers.

Workflow hardening

Use tester feedback to improve setup, project structure, prompt organization, render tracking, review flow, and editor handoff.

Later

Public download and licensing path

Replace or demote tester intake with checkout, customer download access, license entitlement, release manifests, and support workflows.

Later

Production domain cutover

Move from the temporary staging domain to the final ReelCool Studio domain once legal, checkout, and download paths are ready.

Launch gates

Tester intake form works and routes to Tally.
cPanel staging site is updated from the latest static build.
Public copy avoids one-click, bundled-helper, or commercial-clearance claims.
Privacy and terms are reviewed before checkout, analytics, downloads, or account flows go live.
Payment/license/download infrastructure is implemented separately from this static site pass.
Final production domain is connected only after the public release path is ready.

Current staging rule

The temporary staging site lives at reelcool.evil-logician.com. Build locally, upload only the changed static output files when possible, and keep GitHub as the source of truth.

Netlify is optional only. It should not be the primary staging workflow while quota is constrained.

Get setup support

Boundary

The static website is not the app backend.

This site can host marketing pages, tester intake links, documentation, setup guidance, and download instructions when ready. It should not host license secrets, payment logic, user accounts, GPU jobs, ComfyUI services, FFmpeg services, model files, or customer data.