What stays local, what goes through intake, and what is not live yet.

Static content

Website pages

The staging site is built as static Astro output and served from cPanel. It does not run a customer app backend, license backend, or render service.

Hosted form

Tester intake

Tester requests are submitted through Tally. The form is used to review potential testers and contact selected testers by email.

User machine

Local projects

Song files, lyrics, generated media, render attempts, project files, and editor exports are expected to remain local unless the user intentionally moves or uploads them elsewhere.

Not live yet

Future retail services

Checkout, accounts, license activation, production downloads, analytics, and support-ticket services must be documented before public launch.

What tester intake is for

Tester intake is for identifying useful early testers: musicians, editors, producers, AI visual creators, and technical users who can help validate the workflow before public launch.

The form can ask about role, operating system, local AI setup, current tools, song/project readiness, and testing interest.

What not to submit

• Payment-card data or billing credentials through tester intake.
• Passwords, API keys, private model-service tokens, or cPanel/GitHub credentials.
• Confidential client files, unreleased stems, or private music assets unless directly requested under a separate testing process.
• Questions that require legal rights-clearance advice through the intake form.
• Model weights, licensed media packs, or third-party software files.