Start here

Orchestra is an agentic workflow control plane for managing infrastructure across multiple client organizations. This page covers the first 20 minutes after install. The other docs go deeper.

Install

Download the latest Windows installer from the customer portal. Run the .msi. The first launch creates a per-install identity that lives in the Windows Credential Manager — back this up via the Settings page once you're set.

Concepts in 30 seconds

• Tenant — a client organization. Each tenant has its own encrypted database. You manage many tenants from one desktop.
• Department — a logical grouping inside a tenant (e.g. "Production", "Staging", "Customer A").
• Server — a managed Linux box. Bootstrap by SSH'ing it once; an agent installs itself and phones home.
• Workflow — a DAG of nodes. Nodes run commands on agents, call Claude, or pause for human approval.
• Trigger — manual, cron, webhook, or metric-threshold. Cron workflows fire autonomously.

First workflow in 90 seconds

1. Create a tenant (sidebar → Tenants → New).
2. Bootstrap a server by SSH credentials. The agent install takes ~60 seconds.
3. Open Workflows → Templates. Clone "Log Error Scan" into your tenant.
4. Hit Run now. Watch the canvas — every node state transition is live.
5. When Claude's triage node finishes, the result appears in the node output panel.

Where to next

If you're going to run this in production, read the security model next. If you want to connect Slack, PagerDuty, AWS, GitHub, Linear, GitLab, Cloudflare, or Datadog, jump to the integration cookbook. The API reference is for the Tauri command surface (used by the React UI and by any local automation you write against the desktop).