Docs
Start with the workflow you need to run.
Use these docs to evaluate or operate VoxNotch: install paths, local demo, storage, API, admin, backup, monitoring, and production closeout.
- Best for
- Operators and evaluators
- Coverage
- Install, operations, API, admin, storage
- Launch
- Local demo and real-host closeout
Docs map
Choose the path that matches your job.
Install, operate, and back up
Use the download page first, then choose local volume, MinIO, S3, or R2 storage and rehearse backup verification before trusting an instance with real recordings.
Choose hosted or self-hosted
Hosted VoxNotch can use accounts, auth, teams, admin controls, and managed object storage when you want a managed operation instead of a self-hosted one.
Understand the API
Use the developer surface and recipes pages for route-checked curl examples, then follow the runbooks for local operations details.
Run local operations
Use status, monitoring, backup smoke, incident response, and storage docs before a private stack carries recordings that matter.
Check privacy boundaries
Before putting real recordings in any self-hosted stack, read what leaves the box, what can leave if enabled, and what remains your responsibility as operator.
Operating model
The fastest evaluation path is hands-on.
VoxNotch is infrastructure you can run. The docs are organized around commands, checks, and recovery steps instead of broad marketing claims.
Start with one recording, verify the worker, inspect exports, choose storage, and rehearse a restore before adding teammates or automations.
Evaluate with one recording.
The fastest path is still install, run a short file, and inspect the transcript and exports.