Orchestratia
Multi-Repo Workflows

Coordinate Agents Across Every Repository

When your product spans 7 repos and each needs its own AI agent, you need orchestration — not a spreadsheet.

The Multi-Repo Challenge

Modern products are split across multiple repositories: backend, frontend, infrastructure, agents, shared libraries. Each repo might need its own AI coding agent working in parallel.

The challenge isn't running the agents — it's coordinating them:

  • The API agent finishes a new endpoint, but the frontend agent doesn't know it's ready
  • The shared library agent makes a breaking change that downstream agents need to adapt to
  • Three agents all need to update the same integration test suite
  • You need to build the platform Docker images after all component agents finish their work

Without orchestration, you're manually checking each agent and triggering the next step. That defeats the purpose of automation.

Orchestrated Cross-Repo Pipelines

Orchestratia lets you define task dependencies that span repositories. When an upstream task completes, its output automatically becomes input for downstream tasks.

graph LR
    A["API Agent<br/>New endpoint"] --> C["Frontend Agent<br/>Add UI"]
    A --> D["Test Agent<br/>Integration tests"]
    B["DLP Agent<br/>New rules"] --> D
    C --> E["Platform Agent<br/>Docker build"]
    D --> E

    style A fill:#F0F9F7,stroke:#2A9D88,stroke-width:2px
    style B fill:#F0F9F7,stroke:#2A9D88,stroke-width:2px
    style C fill:#FAF8F5,stroke:#E8E3DA
    style D fill:#FAF8F5,stroke:#E8E3DA
    style E fill:#FAF8F5,stroke:#E8E3DA

Contract Exchange

Tasks don't just have ordering dependencies. With Orchestratia's contract system, upstream tasks produce structured output that downstream tasks consume:

  • The API agent outputs the new endpoint schema as a JSON contract
  • The frontend agent receives that schema as resolved_inputs and knows exactly what to integrate
  • The test agent receives both the API schema and DLP rules to write comprehensive tests

This isn't just "wait for completion" — it's meaningful data flowing between agents.

Multi-Repo Tracking

Each server registers its repos. The dashboard shows which agents work on which codebases.

Dependency Graph

Blocking, input, and informational dependency types across any combination of repos.

Contract Exchange

Upstream task output becomes downstream task input automatically via structured contracts.

Cascading Workflows

When a task completes, dependencies auto-resolve and downstream tasks auto-assign.

Coordinate agents across your repositories

Set up cross-repo pipelines with task dependencies and contract exchange.

Get StartedView Documentation

Related Use Cases

AI Coding Agent Orchestration

Stop juggling SSH sessions. Orchestratia gives you a single dashboard to coordinate Claude Code, Gemini CLI, Codex, and any CLI-based AI tool across every server in your fleet.

Learn more

Contracts Between AI Agents

Stop sending vague instructions. Define what agents must deliver, what they receive, and how their output feeds into the next agent.

Learn more

Automated Multi-Agent Pipelines

Define DAGs of tasks. Agents execute in parallel where possible, in sequence where required. Dependencies auto-resolve. Contracts auto-exchange.

Learn more