Local-first evaluators
Try the whole private audio stack before creating vendor accounts.
This path is for buyers and operators who need to prove the product locally: app, API, worker, database, storage, auth smoke, voice previews, backups, and launch evidence.
A local-first evaluation path from command line to healthy app stack.
shell
cd web
./scripts/launch/ops.sh dev --with-marketing
./scripts/launch/ops.sh statusUse the local runbooks to prove the app, API, worker, and marketing frontend together.
A serious local trial has operational proof.
- 01StartBring the dev stack up with dynamic ports and printed URLs.Follow step
- 02SmokeCheck auth, API readiness, worker health, and voice preview release state.Follow step
- 03RecordRun one browser recording and one uploaded file through worker transcription.Follow step
- 04RecoverVerify backup, restore, storage mode, and launch evidence before relying on it.Follow step
Local evaluation paths.
Local demo docsCommands and expectations for starting the local stack.Follow pathOperations docsMonitoring, backup, restore, and launch runbook entry points.Follow pathData custodyUnderstand local volume, MinIO, S3, and R2 choices before importing media.Follow pathSelf-hostingThe responsibilities that come with owning the deployment.Follow path
Local-first means you own more of the system.
Avoiding a managed account does not remove operational work. You still need backups, restore drills, storage configuration, worker health, updates, and incident response.
Hosted beta and self-hosted paths are different custody choices. Evaluate the one you intend to run.
Run the local proof, then decide.
A local trial should produce one transcript, one export, one worker proof, and one backup/restore answer.