Orchestro, and what came before.
Updated Read as Markdown ↗
Orchestro is the product. Older pieces keep their names where the code still uses them.
Orchestro began with a straightforward idea: help people and coding agents turn product ideas into working software. It is now the runtime for autonomous operations: a shared kernel maintains work, evidence, verification and authority across domains. Reliability and Content are the first two proof points.
The ARVO Reliability Factory taught us why active agents do not automatically mean useful progress. Read our story and the lessons behind Orchestro, or explore the core and project packs.
One name across this site
The old landing page, screenshots and installation pitch have been replaced by the product explanation and documentation. Builders run the repair loop; a Content Factory pilot reuses its kernel. General campaign operations remain a direction to validate.
What happens to an existing MCP installation?
An existing mcp-orchestro installation is a separate project. This website does not change its code, data or configuration. Keep using the legacy repository for the documentation corresponding to that package.
The previous npx @orchestro/init command belongs to that package. It does not install Orchestro.
Why do commands say “northstar”?
The current private repository uses northstar as its package command. factoryctl remains a compatibility alias. Orchestro is the public product name; the documentation uses the actual executable names so examples match the code.
Make a fresh connection
Orchestro onboarding starts from your project and its current evidence. There is no automatic migration of legacy tasks, memory or MCP configuration advertised at this stage.
Read the Orchestro quickstart