Features
What orch gives a small team
The work gets shared, and you can see what your Claude capacity is doing.
While a task runs
- Live logs
Follow Claude Code's messages and tool calls. Secrets are masked on the machine before a line leaves it.
- Budgets
A member shares part of their capacity. orch only offers work that fits the 5-hour window.
- Auto or approval
Per project, choose the allowed models and whether tasks start on their own or wait for you.
Keeping everyone informed
- Notifications
In the app, Slack, Discord, any JSON webhook, e-mail or browser push.
- Usage dashboard
Tokens per day, task runs and success rate, over 7, 30 or 90 days.
- History and templates
Search every task that has run, and start new ones from templates.
- Claude Code over MCP
View the pool, split work with dependencies and submit. No extra LLM key.
Yours to run
- One Docker Compose stack
Caddy with automatic HTTPS, the server and Postgres. Cloudflare Tunnel works too.
- Backups built in
Scheduled
pg_dumpwith rotation, optional age encryption and S3 upload. - Observability on request
Prometheus metrics and OpenTelemetry traces, off by default.
- Sign-in you control
GitHub sign-in limited to admins, an allowlist of logins or organizations, and invite links.
Security
For teams who trust each other.
A shared to-do list with automation, not a multi-tenant platform.
What it does not do
- Not for strangers
Anyone who can label an issue for the pool is, in effect, writing a prompt that runs on a teammate's machine.
- A root-equivalent agent
It drives Docker on the member's host to start task containers. Rootless Docker reduces this.
- Exact budgets
Usage and budgets are estimates, so treat them as hints.
- Other platforms
GitHub only, English interface only, and a single server instance.
Get orch running
One Docker Compose stack with automatic HTTPS. Details are in the docs.
$ git clone https://github.com/selfhostr/orch.git
$ cd orch/deploy/server && cp .env.example .env
$ docker compose up -d