Commercial license
Request the right to run VoxNotch in your workflow.
This is not a checkout for a generic SaaS seat. A commercial request should describe the instance you want to operate, the audio workflow you need to prove, and the subscriptions or usage meters you want to stop renting.
- Primary path
- Perpetual code license
- Current status
- Beta commercial requests
- Hosted access
- Separate operator agreement
- Fastest review
- One workflow, one storage mode, one buyer owner
Process
What a good request includes.
Choose the package
Personal Operator, Studio / Team, Commercial Source, or Operator Support. If you are unsure, describe the workflow and the package can follow.
Name the private workflow
Transcription archive, podcast production, captions, narration, voice design, watch-folder automation, or agentic workflow operation.
State the custody boundary
Local volume, MinIO, S3, R2, hosted beta, or not sure yet. Storage and egress are part of the quote because they change the operational responsibility.
List what you are replacing
Subscriptions, metered minutes, TTS characters, transcription credits, manual exports, or fragile scripts. The ownership argument works best when the replaced cost is visible.
Request types
Pick the commercial conversation.
| Path | Use when | Next step |
|---|---|---|
| License request | You want to buy a perpetual right to run the code in your own environment. | Send package interest, operator owner, and target workflow. |
| Support request | You want help standing up the stack, proving backups, or planning migration. | Bring current storage, expected audio volume, and launch deadline. |
| Hosted beta request | You need managed access before your organization can operate infrastructure. | State media sensitivity, storage preference, and support boundary. |
Send the commercial-license request.
The email draft asks for package interest, workflow, deployment mode, storage mode, and the rented services you want to replace.