Docs
Launch confidence starts with one real workflow.
Use invite-first access when you want storage, backups, support, abuse handling, and operator monitoring reviewed against your actual workflow before broader rollout.
- Access
- Invite-first
- Evaluation
- One workflow end to end
- Support
- Metadata-only admin
Four launch gates matter most.
A named workflow
Start with one recording, archive, episode, caption track, voice run, or automation path.
A custody mode
Choose local, MinIO, S3, or R2 before real media enters the stack.
A restore drill
A backup that has not been verified is a hope, not a recovery plan.
A support boundary
Admin can see metadata and health. It should not read private content or impersonate users.
Evaluation links for a buyer walkthrough.
Local demoConfirm the app URL, API URL, marketing URL, auth smoke, and dynamic ports before a buyer walkthrough.Follow pathStorage custodyName the storage mode before real media enters the stack: local volume, MinIO, S3, or R2.Follow pathOperationsUse worker, queue, backup, restore, and monitoring checks as operating evidence rather than promises.Follow pathCommercial licensePosition VoxNotch as buy-the-code infrastructure with optional support, not a usage-meter SaaS.Follow path
shell
marketing/scripts/ops.sh urls
marketing/scripts/ops.sh launch-gates
cd marketing/web && npm run perf:launchThe marketing gate prints the resolved site URL and, when present, app/demo URLs from the sibling app environment files.