You are viewing the docs for Archestra v1.4. View the latest docs
Admin
Administrators operate an Archestra instance and manage who can use its resources. Start with Deployment to install the platform and connect a database.
For organization access, assign roles and resource grants, then connect an identity provider for sign-in and team membership. Use environments to separate resource access, deployment permissions, and network policies.
Protect stored credentials with Data Security. Observability covers logs, metrics, and traces for checking platform health and investigating requests. Settings available to operators are listed in Configuration.
Explore
Deployment
Install Archestra with Docker or Helm and configure production access
Access Control
Assign roles and share resources with users, teams, and service accounts
Environments
Isolate tools, knowledge, skills, subagents, runtimes, and cost limits across deployment environments
Identity Providers
Connect Okta, Microsoft Entra ID, Google, GitHub, GitLab, or any OIDC or SAML provider for sign-in and per-user tool access
Logs and Auditing
See every model request, tool call, and admin change, and choose who can read them and how long they stay
Observability
Export Archestra metrics, traces, logs, and usage events to your monitoring stack
Data Security
Protect stored credentials, external secrets, and encrypted content
Roll Out Usage Accounting
Activate component billing without resetting existing budgets.
Upgrade from v1.3 to v1.4
What v1.4 changes for your deployment, what it deletes, and the exact steps to upgrade from v1.3 with Helm or Docker