Buyer memo
A one-page case for buying the code.
VoxNotch is purchased as software ownership, not rented as another audio AI account. This memo gives a buyer, operator, or reviewer the short version: what is bought, what it replaces, what remains your responsibility, and what must be checked before rollout.
- Model
- Perpetual commercial code license
- Use case
- Private STT, TTS, media production, and automation
- Privacy posture
- Local by default; egress explicit
- Launch contact
- [email protected]
- Use browser print to save as PDF
Memo
The buyer argument.
Problem
Sensitive audio workflows are split across hosted transcription, editing, voice, captioning, storage, and automation products that charge recurring usage meters and require media custody handoffs.
Purchase model
Buy a perpetual code license, run the instance in your environment, and keep using the purchased version without per-minute or per-character application billing.
Operational responsibility
The buyer still owns hardware, storage, backups, restore drills, updates, optional cloud services, and launch support unless those are covered by a separate agreement.
Decision test
Approve when one real recording can move from capture to transcript, review, output, automation, backup, and restore inside the chosen custody boundary.
Approval table
What to review before purchase.
| Area | Question | Proof path |
|---|---|---|
| License | Does the commercial license grant the exact right to run, modify, and operate the code you need? | Review /license and the signed order. |
| Economics | Which subscriptions, minutes, characters, seats, or manual workflows does ownership replace? | Use the ROI calculator on /pricing. |
| Privacy | Where does media live and which paths create egress? | Review /privacy and /data-custody. |
| Operations | Who owns uptime, backups, restores, upgrades, storage, workers, and monitoring? | Review /commercial-support and /docs/operations. |