Hosted or self-hosted
The same private audio workflow can run close or managed.
Self-hosting remains the strongest custody story. VoxNotch also has the account, auth, admin, monitoring, and backup primitives needed for a more available hosted deployment when the operator is explicit about storage and support boundaries.
A local workflow with room for an operator-managed deployment boundary.
Deployment modes
What changes when VoxNotch is hosted.
| Question | Self-hosted | Hosted |
|---|---|---|
| Who operates the stack? | You run Docker, storage, backups, monitoring, and upgrades. | The service operator runs the stack and must publish its storage, backup, support, and abuse policies. |
| Where does media live? | On your machine by default, or in object storage you configure. | In the hosted operator storage mode: local fleet storage, MinIO, S3, or R2. |
| What auth exists? | Local accounts, invites, reset, verification, refresh tokens, and TOTP. | The same first-party auth primitives, plus hosted onboarding and support policy. |
| What stays separate? | You do not need billing, seats, or plan enforcement for a personal instance. | Hosted billing, quotas, subscriptions, and plan enforcement belong in a managed-service agreement, not the self-hosted code license. |
Hosted must-haves
Before hosted access, prove the operator path.
Invite-first onboarding
Run with invite or closed registration until abuse controls, support, legal pages, and storage policy are proven.
Metadata-only support
Admin can see accounts, counts, jobs, safe error codes, and audit events. It cannot impersonate users or read content.
Remote storage disclosure
If S3 or R2 is used, say so plainly. That storage is a deliberate media custody choice, not the local-only default.
Recovery evidence
Run backup, verification, and restore drills before inviting users whose recordings matter.
Hosted questions
Does hosted VoxNotch require Supabase?
No. The product has first-party local auth primitives. Supabase-compatible auth is optional only if an operator intentionally enables that provider path.
Is hosted access the same as buying the code?
No. Buying the code is a perpetual license model. Hosted access is a managed-service path with its own storage, support, backup, and custody boundaries.
What should be proven before hosted users upload media?
The operator should prove invite-first onboarding, storage disclosure, backup verification, restore rehearsal, worker health, and metadata-only support boundaries.
Join the beta when your workflow needs the hosted path.
Beta access should start with one real workflow, a clear data custody mode, and an operator who can explain storage, backup, support, and egress before users upload sensitive media.