Workspace settings
Private by default. Enable execution only after reviewing your deployment.
Public preview. Sign in with the configured Clerk owner account to access private settings and execution.
Access & spending
- Allowed account
- Configured owner only · Clerk
- Paid execution
- Disabled / not connected
- Concurrency
- One active run at a time
- Live sessions
- 60-second pilot · disconnect requests termination · no state resume
Provider connections
Credentials never belong in your browser. Configure website secrets in Vercel and provider/storage secrets in the private backend’s deployment settings, then redeploy the affected services.
World LabsLegacy Marble integration · outside the WASD pilotPrivate
ModalLive-world workers · one H100 per run · scales to zeroPrivate
RunpodLegacy provider · preserved for existing recordsPrivate
Hugging FaceApproved model assets only · no runtime downloads in new workersPrivate
Cloudflare R2Private inputs and durable outputsPrivate
Deployment profilesPinned images, prices, rights and smoke-test evidencePrivate
“Configured” means a setting is present, not that credentials or deployment behavior have been verified.
Enable a model safely
- Configure owner sign-in, PostgreSQL and private R2 storage.
- Review the model’s license and pin its code, container and checkpoint revisions.
- Add a deployment profile with a current price ceiling and expiry. Approve persistent storage separately.
- Start the API, orchestrator and independent cleanup service. Confirm backups and alert delivery.
- Approve a real verification run in the playground. Only after validating its outputs and hardware should you record its run ID in the profile.
Deployment commands, secret names and acceptance checks are in docs/deployment.md.
Costs outside a run
Railway services, database backups, R2 storage and retained model caches can incur ongoing charges even when no GPU is running. This application does not reconcile their invoices.
Cost ceilings are safeguards, not billing guarantees. Provider rounding, shutdown delays and noncancelable jobs can add charges. A failed shutdown remains visible in run history and operator logs.