Source: https://www.orchestro.org/docs
Updated: 2026-10-04

# A shared kernel for different missions.

Updated October 4, 2026[Read as Markdown ↗](https://www.orchestro.org/docs.md)

Orchestro is the control plane for autonomous software agents. It maintains persistent AI-agent loops with durable state, work selection, recovery, independent verification, production feedback and learning. Your models supply intelligence and agent harnesses execute; Orchestro keeps the work and evidence connected. Super private beta, primarily used on our own internal projects. The preview is free with hands-on onboarding; users supply their own agents, subscriptions and infrastructure. Public self-service access and broader unattended autonomy remain in development.

The same kernel runs a Reliability Factory and a manually configured Content Factory pilot. A domain adds its work vocabulary, evidence, policy, adapters and completion rules. The kernel keeps durable state and constrains effects while agents choose a method.

## Same kernel. Different domain.

Workflow automation says “when X, do Y”. An agent completes a task. Orchestro maintains a mission over time: observe, understand, select, strategize, execute, verify, learn and create the next work.

Goal-based scaffolding and Domain Builder V1 exist in the private core; public self-service onboarding is in development. [Read the two-domain proof](https://www.orchestro.org/story#content-factory) or [check live capabilities versus roadmap](https://www.orchestro.org/docs/roadmap).

## In Reliability: start with the user’s job

“Sign up” is a product capability. The form, authentication service and verification email are the pieces behind it. Factory links them so a technical issue has a human context.

User goalProduct capabilityCode + evidence

## Keep two questions separate

*   **Did the change work?** Check the actual released behavior, with verification separate from the agent that made the change.
*   **Did it help?** Look at a meaningful user or business outcome. An improvement in a metric alone does not prove what caused it.

**Understand the loop. Then see a real Factory.**

[How it works](https://www.orchestro.org/how-it-works) pairs the owner view with the machinery underneath. [Live Factories](https://www.orchestro.org/live) reads a dedicated public projection: Content is connected; ARVO is Coming online. Every observation has a timestamp. Missing or stale data is never replaced with sample activity.

The older product and marketing walkthroughs remain in [illustrative operating examples](https://www.orchestro.org/docs/operating-examples). Their sample metrics explain the model; they are not live results.

## Get oriented

[**Factory lifecycle**A report in the backlog is not a promised PR. Follow classification, shared problems, selection, root cause, verification, evidence waits and the distinction between Backlog Zero and Operational Zero.](https://www.orchestro.org/docs/factory/lifecycle)[**Quickstart**Set up Orchestro, check your coding CLI and connect a project in observation mode.](https://www.orchestro.org/docs/quickstart)[**How the loop works**How Orchestro connects product mapping, recommendations, owner decisions, agent work and verification.](https://www.orchestro.org/docs/how-it-works)[**Your loop**One kernel maintains different missions. See the historical Reliability and Content pilots, the current Content observation, and the private Domain Builder foundation for public self-service setup.](https://www.orchestro.org/docs/loops)

**Early access, actively being built.**

The private owner cockpit is deployed, and Content has a public read-only view. Product illustrations remain labelled separately. The [availability page](https://www.orchestro.org/docs/roadmap) distinguishes deployed preview capabilities, historical proof and remaining work.