Deploy

Harness is an in-process TypeScript library, not a hosting platform. Deploy the HTTP worker, queue consumer, CLI, or other host you build around it using your normal application platform.

Production responsibilities

• Supply provider credentials and provider-specific headers through your platform's configuration system.
• Choose durable storage for session records and active/deferred work when sessions must survive a process restart.
• Authenticate and authorize every public transport endpoint before creating or resuming sessions.
• Apply timeouts, cancellation, retries, and rate limits around provider and service calls.
• Persist or forward SessionRecord and observation events to the logs, traces, or metrics systems your team operates.
• Restrict Studio to loopback development use; do not publish it as an unauthenticated dashboard.

Keep the host portable

The same built agent can run behind a web server, in a worker, or in a background process. Keep transport and deployment adapters outside your capabilities so that changing a deployment target does not change the model-and-tools loop. Your host decides how to map requests into session.input(), persist records, and deliver output to clients.

There is no managed Harness deployment service. This boundary is intentional: your provider accounts, credentials, data retention, and runtime topology remain yours.