Pricing
Buy the code. Run it where your audio already belongs.
VoxNotch is not positioned as another rented transcription SaaS and it is not pretending to be free. The intended model is old-school software: pay once for a perpetual license to the code, operate it in your own workflow, and stop sending every recording through metered services by default.
Guide price from $495 once. Your machine, your storage, your workers.
Code ownership model with local audio workflows and subscription meters removed.
The offer
Own the working system, not another monthly permission slip.
A VoxNotch purchase should grant the right to run the product code for your own organization, keep the instance in your infrastructure, and build local workflows around it without asking a vendor meter for permission.
You still pay for your own hardware, storage, backups, and optional cloud providers. The difference is that those costs are infrastructure choices, not a transcription or voice bill that grows every time the archive gets useful.
Model
What you buy, what you do not rent.
| Question | Perpetual VoxNotch license | Typical audio SaaS |
|---|---|---|
| Payment shape | One purchase for the code license. Optional support, hosted operation, and major-version upgrades are stated separately. | Subscription plans, per-seat charges, usage credits, minutes, characters, or AI-agent meters. |
| Where work runs | Your Docker stack, workers, storage, and backup routine by default. | Vendor infrastructure by default, with your media crossing the service boundary. |
| What scales the bill | Your hardware, electricity, and storage choices. | More recordings, longer archives, more synthesis, more users, or higher AI usage. |
| What you keep | The code, local configuration, media, transcripts, generated outputs, and workflow history inside your instance. | Account access to a hosted product while the subscription and vendor terms continue. |
| Privacy boundary | Audio stays in your chosen custody mode unless you explicitly configure remote storage or cloud models. | Upload, retention, model, support, and deletion behavior follow the provider policy and plan. |
Packages
Commercial license packages.
These are guide prices for buying and operating VoxNotch as software you own. Final quotes depend on license scope, support level, and whether you need hosted operation.
| Package | Guide price | Includes |
|---|---|---|
| Personal Operator | $495 once | One owner-operated instance, local workflows, private media storage, transcripts, TTS/STT surfaces, exports, and access to the purchased code version. |
| Studio / Team | $1,950 once | One organization-operated instance, multiple internal operators, automation workflows, S3-compatible storage modes, admin controls, and commercial workflow use. |
| Commercial Source | $4,900 once | Broader internal modification rights, private deployment review, implementation planning, and a written boundary for what is not redistributable or resold. |
| Operator Support | From $750 per engagement | Setup help, migration planning, backup and restore drills, upgrade support, storage review, and launch-readiness checks. |
Prices are commercial guide prices, not a self-service checkout. Hosted access, custom terms, regulated deployments, and resale rights require a separate agreement.
ROI worksheet
Estimate the payback from replacing rented audio AI.
Change the numbers to match your stack. The point is not fantasy savings; it is seeing when local ownership beats recurring minutes, characters, seats, and usage overages.
Ownership worksheet
- Monthly SaaS replaced
- $378
- Net monthly recovery
- $343
- Upfront ownership cost
- $2,550
- Estimated payback
- 8 months
- Year-one delta
- $1,566
- Two-year delta
- $5,682
This is a planning estimate, not a quote. It deliberately includes infrastructure because owning the code still means operating the stack.
Why pay once
The economics improve when the workflow is real.
A perpetual license is not a magic discount. It makes sense when private audio work is recurring, sensitive, automated, or expensive enough that renting every step becomes the wrong shape.
Save on usage meters
Long recordings, archive backfills, captions, previews, and retry-heavy workflows should not require counting every minute, character, or generated artifact.
The meter becomes local compute and storage.
Keep implementation local
Build watch folders, webhooks, destinations, scripts, and agent runs around an instance you control instead of a changing external API and plan table.
Your workflows survive vendor packaging changes.
Protect sensitive media
Private practice, research, legal-adjacent, internal, and unpublished media can be processed without default upload to a transcription or voice vendor.
Remote storage and cloud models remain explicit choices.
Own the escape hatch
Because the product is deployed in your environment, backup, restore, export, and shutdown are operator procedures rather than support tickets.
Ownership is operational, not just contractual.
No vendor account
No Supabase account required.
VoxNotch uses first-party local auth and a Postgres database in the stack you operate. The commercial model is not built around requiring a Supabase project, a hosted auth account, or a vendor dashboard before private media can enter the workflow.
If a hosted deployment is chosen later, that is a managed-service decision with its own storage and support boundary, not a hidden prerequisite for running the code.
Ownership
What you own after purchase.
| Asset | What ownership means | Why it matters |
|---|---|---|
| Application code | You can keep running the purchased version under the license terms. | Your workflow does not vanish because a subscription, plan, or vendor package changed. |
| Configuration and workflow glue | API keys, watch folders, destinations, webhooks, prompts, and runbooks live with your instance. | Automation becomes local infrastructure instead of an external service dependency. |
| Media and transcripts | Recordings, transcripts, notes, tags, exports, and generated outputs stay in your chosen storage boundary. | You can back up, restore, audit, and delete the actual work without asking a vendor. |
| Operational history | Jobs, runs, failures, queue state, and admin events remain inspectable inside your deployment. | A private media system is only trustworthy if the operator can prove what happened. |
Boundaries
Perpetual does not mean everything forever.
A clean old-school license should say exactly what is included: the code version purchased, the right to run it for the licensed owner, and the right to keep using that version indefinitely.
It should also say what is separate: hosted operations, hands-on support, managed backups, model weights that carry their own licenses, third-party cloud storage, and future major-version upgrades if those are sold separately.
That distinction keeps the promise believable. “Pay once and own it forever” should mean you can keep running the purchased code indefinitely, not that every future service, model, support commitment, and hosted resource is included forever.
Remaining costs
What you still pay for.
| Cost | Why it remains | How to control it |
|---|---|---|
| Hardware and electricity | The STT/TTS work runs somewhere, even when it is not rented from a vendor. | Start with the local demo, then size CPU/GPU only for workflows that prove value. |
| Storage and backups | Private media still needs durable disks, object storage, backup verification, and restore practice. | Use local volume first; move to MinIO, S3, or R2 only when the custody trade-off is deliberate. |
| Optional cloud models | Some LLM or provider-backed voice paths may still carry third-party usage costs. | Keep no-cloud defaults, explicit egress labels, and separate provider keys. |
| Support and upgrades | Perpetual use of one purchased version is different from unlimited labor and every future major release. | Buy support when launch risk, migration, backup drills, or private deployment review justify it. |
Pricing questions
Is VoxNotch free?
No. The proposed pricing model is paid software: buy a license to run the code. Free trials, demos, or beta access can exist, but the product should not be positioned as free.
Is this SaaS?
The core offer is not SaaS. The core offer is a perpetual code license that you run in your own environment. A hosted beta can be offered separately, with its own custody, support, and storage terms.
Does pay once mean no future costs?
No. You still operate the stack and pay for hardware, storage, backups, electricity, optional cloud services, and optional support. Pay once means the application license is not metered per minute, per character, or per generated output.
Can I modify the code?
That depends on the final license text. The pricing page should not promise modification, redistribution, resale, or managed-service rights until the commercial license says so plainly.
Commercial boundary
- The pricing model is paid software: buy a license to run the code, scope support separately, and treat hosted operation as a separate service boundary.
Start with the workflow you want to stop renting.
The best pricing conversation is concrete: one archive, one production workflow, one automation path, and the subscriptions or usage meters you want to replace.