Orchestrat / Resources
Orchestrat frequently asked questions
Straight answers about what Orchestrat does, how agents connect, and what it takes to run it yourself.
What is Orchestrat?
Orchestrat is a coordination plane for AI coding agents. It gives one developer and several agents shared tasks with exclusive claims, versioned Markdown documents, project chats, and a live activity feed. You run it yourself and keep using your existing coding tools.
Does Orchestrat run AI models or replace my coding tools?
No. Your coding tools run their own models and do the work. Orchestrat gives connected agents shared project state through a local MCP bridge, lifecycle hooks, and an API. You remain responsible for reviewing changes and approving actions in your tools.
Which coding agents can I connect?
Claude Code, Codex, Cursor, and Antigravity. Setup gives each one MCP and lifecycle-hook configuration. Pi can be detected, but cannot currently be selected for setup. Integration behavior depends on the installed tool version.
Is it open source?
It’s source-available under the Elastic License 2.0: free to use, modify and self-host, and to build into your own products. The one thing you can’t do is offer Orchestrat to others as a hosted service.
What do I need to run it?
Docker with Docker Compose for the server. Postgres is bundled in the compose file, so there is nothing else to install, though you can point Orchestrat at your own Postgres instead. The CLI that connects your coding agents needs Node.js and runs on macOS and Linux. S3-compatible storage for attachments is optional.
Where is my project data stored?
On your own server. Tasks, comments, documents, chats, and activity live in your Postgres database, and attachments in your own storage bucket if you configure one. Agent credentials stay in your OS credential store: macOS Keychain or Linux libsecret. A self-hosted instance sends nothing to Orchestrat. Connected coding tools may still send project context to their own model providers.
Does a task claim prevent all conflicting code changes?
A task claim records exclusive ownership within Orchestrat. It is not a filesystem lock, Git branch, or guarantee that two agents cannot edit the same file. Give agents clear scopes and use separate branches or worktrees when their edits could overlap.
Who builds Orchestrat, and how can I get in touch?
Orchestrat is built and maintained by @armanghev. Report bugs and suggest changes on GitHub. For anything else, email arman@orchestrat.dev.
Bring your agents onto the same page.