- Tasks are GitHub issues. A member, or Claude Code through MCP, adds them to a shared pool.
- Each task runs on a teammate's own machine, with their own Claude subscription, in a throwaway container that only sees its own git clone.
orchpushes a branch and opens a PR. - Docs: orch.selfhostr.io/docs. Changes: CHANGELOG.md.
Free, for good. MIT licence, no paid edition.
Try the demo first if you like. Server admin, once (Linux host, Docker 26+ with Compose, ports 80 and 443, a DNS name pointing at it):
- Create the GitHub App and save its private key as
deploy/server/secrets/github-app.pem. This must happen before the first start, otherwise Docker creates a directory with that name. GenerateGITHUB_WEBHOOK_SECRETfirst (openssl rand -hex 32): it is also the App's webhook secret. See GitHub App. - Fill in
.env: at leastORCH_DOMAIN,ORCH_ADMIN_GITHUB_LOGINS, the generated secrets and theGITHUB_*values of the App: installation. - Start the server:
git clone https://github.com/selfhostr/orch.git && cd orch/deploy/server
cp .env.example .env # edit it as in step 2
docker compose up -dEach member then runs the one-time command (valid 15 minutes) from My Server in the web UI:
curl -fsSL https://<domain>/install.sh | ORCH_TOKEN=<one-time-token> sh
orch loginSign in at https://<domain>. Back up the database dumps and keep .env (notably ORCH_ENCRYPTION_KEY) and the GitHub App private key elsewhere: they are not in the dump. Full steps: quick start, installation.
- No pooled accounts. The server never sees Claude credentials; member machines connect out over a WebSocket, so no inbound ports.
- Pool and Backlog. Issues with the project's pool label become tasks; budgets are estimates.
- Auto or approval. In
AUTOthe agent runs a task headlessly and the PR opens as a draft; inAPPROVALnothing starts until the member accepts. - Manual mode.
orch take <n>,orch attach <n>,orch done <n>in ascreensession. - Claude Code over MCP. Submit and inspect tasks with MCP OAuth 2.1 or personal access tokens.
- Access control. Admins, allowlists of logins or organizations, access requests, invite links.
- Notifications and observability. In-app, browser, e-mail and webhook notifications; Prometheus metrics and OpenTelemetry traces.
- Backups. Scheduled
pg_dumpwith rotation, optional age encryption and S3 upload.
Caddy (automatic HTTPS, static web build) fronts a Fastify server with Postgres; scheduled dumps run in a backup service. Each member runs an agent container that drives their local Docker and starts one non-root task container per task, with only its clone mounted. See concepts.
- For teams who trust each other: anyone who can get an issue labeled for the pool can write a prompt that runs on a teammate's machine. Do not use it with strangers or public repos.
- In auto mode the task container runs with
bypassPermissions, network access and the member's Claude token, with no egress filtering. - The agent is root-equivalent on the member's host (it mounts
/var/run/docker.sock); rootless Docker reduces this. - Single server instance by default; usage and budget are estimates. GitHub only. The web UI is in English and French.
- The agent image installs Claude Code, which is proprietary software from Anthropic and is subject to Anthropic's terms; orch itself is MIT-licensed.
- Releases are
0.x: anything may change between minor versions. See the security model.
Issues and pull requests are welcome: CONTRIBUTING.md. Security issues: SECURITY.md.
MIT, see LICENSE. Provided "as is", without warranty of any kind.
orch is free and has no company behind it. If it saves you time, you can support its development:
Sponsor us on GitHub, recurring or one-off.