Open source · Desktop app
Delegate to AI. Keep track.
Delegate to AI. Keep track.Today is one screen for all your projects. It shows what needs your answer, what to pick up again, what is running now, and what comes next.
- MIT license, with Enterprise Edition modules under BUSL-1.1
- Free to download. Needs Docker Desktop and Claude Code.
- macOS, Windows, Linux
A request from an assistant arrives, you approve it, the assistant gets back to work, a task is completed and the plan moves forward.
Today · Sunday 4 October
An assistant is waiting for your answer
It has been waiting for 1 min.
17/38 tasks done
across 3 plans tracked here
- 4 in progress
- 1 waiting for your answer
- 1 blocked
- 15 upcoming
Waiting for you1
- QuestionWelcome dinner and menuEvents
The caterer offers two menus for 24 guests. Which one should I confirm?
Free conversation: not attached to any plan
Open the conversation
To pick back up1
- Prepare the funding applicationTask blockedFundingfor 2 d$2.405/121 blocked
Resuming reruns 2 tasks; 5 already done
1 blocked task will be skipped
- Get the signed partner letter
Unblock them before resuming: a blocked task is skipped.
My tasks
- Confirm the venue depositDoneOrganise the autumn team offsite
- Send the save-the-date to guestsDoneOrganise the autumn team offsite
- Pick the menu for the welcome dinnerWelcome dinner and menu
- Book the train ticketsOrganise the autumn team offsite
In progress2
- Organise the autumn team offsite1h 16m$5.8510/183 in progress3 assistants are working on itEvents
- Welcome dinner and menu28m$2.052/81 waiting for your answer1 in progress1 task is waiting for your answerEvents
Assistants
1 waiting for your answer · 3 working
$5.50
Proposals 1
- Share the budget sheet with the whole team
Decisions 1
- Hold the offsite in November rather than October
Notes to review 1
- The lodge is closed on Mondays
A request from an assistant arrives, you approve it, the assistant gets back to work, a task is completed and the plan moves forward.
Today · Sunday 4 October
An assistant is waiting for your answer
It has been waiting for 1 min.
17/38 tasks done
across 3 plans tracked here
Waiting for you1
- QuestionWelcome dinner and menuEvents
The caterer offers two menus for 24 guests. Which one should I confirm?
Free conversation: not attached to any plan
Open the conversation
In progress2
- Organise the autumn team offsite1h 16m$5.8510/183 in progress3 assistants are working on itEvents
- Welcome dinner and menu28m$2.052/81 waiting for your answer1 in progress1 task is waiting for your answerEvents
Assistants
1 waiting for your answer · 1 working
$5.50
Built on open tools you can inspect
31
MCP tools
Each tool takes an action parameter: plan, task, note, decision, code…
17
tree-sitter grammars
Rust, TypeScript, Python, Go, Java, C, C++ and more, parsed into the graph.
3
desktop platforms
The Tauri app ships for macOS, Windows and Linux.
The problem
Three things go wrong when your AI assistants share no memory
Scroll through each one. First you see what happens. Then you see what Project Orchestrator keeps so it stops happening.
1 / 3
Your assistants start from zero in every conversation
You explain your goals, your preferences and what was already decided. Then the chat closes and the assistant forgets it all. Next time, you explain it again.
With Project Orchestrator
PO keeps your notes and decisions with the project. Before a task, the assistant looks up what applies. It searches by meaning, not only by exact words.
Under the hood
Notes and decisions are stored in a graph in Neo4j. note(action: "search_semantic") finds them by meaning, with Meilisearch.
2 / 3
Assistants change the same thing at the same time
Two assistants edit the same document. One starts a job before the job it needs is done. So you do one thing at a time, and you lose the time you wanted to save.
With Project Orchestrator
A plan says which task depends on which. Tasks that do not depend on each other go at the same time. The others wait for the tasks they need.
Under the hood
PO computes waves from the task dependencies with plan(action: "get_waves"). Tasks that declare the same affected files are split into different waves.
3 / 3
The reason behind your choices gets lost
Why this place, why that budget. The reason stays in someone’s head or in an old message. The next assistant asks again, or undoes the choice.
With Project Orchestrator
A decision is saved with its reason and what it affects. The next assistant finds it, with its status, before it changes anything related.
Under the hood
A decision is linked to the tasks, plans or files it affects with decision(action: "add_affects"), and it has a status such as proposed or accepted.
One plan, two views
Do several tasks at once, not one after another
Some tasks need another task to be done first. The others can start together, as a group called a wave. Watch the same plan as a map of links or as a board with columns.
Organize the team weekend
0/8 done (0%)
- Wave 12 in parallel, 6 min
- Wave 22 in parallel, 14 min
- Wave 33 in parallel, 12 min
- Wave 41 in parallel, 7 min
Shortlist three venues near a train station
Collect everyone’s availability
Book the venue
Write the invitation
Plan the two-day schedule
Arrange meals and transport
Send invitations and track replies
Share the final plan with the team
One assistant, task by task
71 min
In waves
0 min / 39
Time saved
—
Run the plan to measure it
Illustrative scenario: the durations are assistant minutes written for this demo, not a benchmark.
What it does
Your projects, plans and decisions in one place
Projects with or without code, plans, assistants that work together, a memory of what was decided, and sharing only with your consent. Each one is shown below.
Memory
PO remembers what you decide and learn
Notes, decisions and the links between them stay attached to your project. PO finds them again when they are useful. Scroll to watch a memory grow.
Invented example: a small event project. The names in the graph are illustrations, not your data. Colors and shapes are those of the product graph.
1 of 5
Your files become dots
PO starts from what is in the project: documents, spreadsheets, files. Each one is a blue dot.
2 of 5
Plans and tasks join in
Plans and tasks are added to the same picture. Each task is linked to the files it touches.
3 of 5
Notes and decisions stay linked
What you learn becomes a note. What you decide becomes a decision. Both stay linked to the files and to each other.
4 of 5
Related things group together
Items about the same subject move close to each other. You see the main themes of the project at a glance.
5 of 5
PO finds the answer along the links
You ask a question. PO finds the notes that match (cyan). Then it follows the links to related items (violet), even when the words are different.
Under the hood: the names of the links
These are the names the product uses for the links in its graph. You do not need them to use PO.
- CONTAINSA plan contains its tasks.
- IMPORTSA file uses another file.
- AFFECTSA task touches a file.
- CO_CHANGEDTwo files that often change together, seen in the history of the code.
- SYNAPSEA link between notes, decisions and files. Links nobody uses fade away.
How it works
From one sentence to checked work
Plan, order, recall, run, verify, learn. This is what PO does for every plan.
1 · Plan
You say what you want, you get a plan
You describe the result in one sentence. The assistant turns it into a plan with tasks. Each task has steps, and each step says how to check it is done.
2 · Order
Tasks that do not depend on each other go together
PO sorts the tasks. A task waits only for the tasks it needs. All the others can start now, at the same time.
3 · Recall
The assistant looks up what the project already knows
Before each task, the assistant reads the notes and decisions that apply. So it does not ask the same questions again.
4 · Run
Assistants do the tasks, group by group
Each task goes to its own assistant. The tasks of a group run at the same time, and the next group waits.
5 · Verify
A group is done when its checks pass
Before the next group starts, PO checks the work. The steps must be closed and no sensitive file may be left in the changes. For a code project, PO also checks that it still builds.
6 · Learn
What was learned is saved for next time
When the work is done, what was decided and learned is written back to the project memory. The next plan starts with it.
What stage 6 saves is what stage 3 recalls on the next plan.
Follow one run, stage by stageTry it
Watch an assistant work with PO
Pick a request. You see the answer in plain words, and the calls the assistant makes to PO behind the scenes. Open a call to see its details.
Two notes apply: the place must be close to a train station, and last year the menu had nothing vegetarian. I will write the plan around both.
The plan has 3 tasks in 2 waves. The shortlist and the date poll do not depend on each other, so they happen at the same time. Booking waits for both.
Simulated demo: the answers are scripted and no server is contacted. The calls and their arguments are the real ones.
Where PO is going
Each person keeps their PO. The organization shares what it chooses.
Think of a company: a common knowledge, teams, people and access rights. Part of the base runs today. The organization layer is planned.
Illustration with invented people.
Available
One PO per person: own identity, sign-in, workspaces, vault
In progress
Sharing between PO instances, only with consent
Planned
Common knowledge, teams and roles, access rights
Download
Download Project Orchestrator
Pick the app for your computer. There is no Project Orchestrator account to create.
Before you start
- Docker Desktop. The app uses it to run the services it needs, and it can help you install it.
- Claude Code, which powers the chat. The AI is not included: you need your own Claude account.
- The first launch takes a few minutes. A setup wizard guides you and downloads what is missing.
Linux 5
- Linux, AppImage126 MBOne file that runs on most Linux distributions (x86_64).Project.Orchestrator_0.0.16_amd64.AppImage
- Debian and Ubuntu, x86_6458.1 MBPackage to install with dpkg or apt.Project.Orchestrator_0.0.16_amd64.deb
- Debian and Ubuntu, arm6452.7 MBPackage to install with dpkg or apt, for ARM64 machines.Project.Orchestrator_0.0.16_arm64.deb
- Fedora and RHEL, x86_6436.7 MBPackage to install with dnf or rpm.project-orchestrator-0.0.16-1.x86_64.rpm
- Fedora and RHEL, arm6430.7 MBPackage to install with dnf or rpm, for ARM64 machines.project-orchestrator-0.0.16-1.aarch64.rpm
orchestrator, orch and mcp_server, with the web interface included. Lighter versions without it are on the release page.
For developers: command line
Homebrew
Mac and Linux. Installs orchestrator, orch and mcp_server.
brew install this-rs/tap/project-orchestratorInstall script
Mac and Linux. Latest release into ~/.local/bin. Add --no-frontend for the light variant.
curl -fsSL https://raw.githubusercontent.com/this-rs/project-orchestrator/main/install.sh | shPowerShell
Windows. Installs into %LOCALAPPDATA%\orchestrator\bin.
irm https://raw.githubusercontent.com/this-rs/project-orchestrator/main/install.ps1 | iexDocker
Image for amd64 and arm64, with the web interface.
docker pull ghcr.io/this-rs/project-orchestrator:latest# API only, no dashboard: a version tag with the -api suffix# docker pull ghcr.io/this-rs/project-orchestrator:0.0.16-apiWhat the server needs
- Project memory
- Neo4j 5
- Search
- Meilisearch
- Event bus
- NATS (optional)
- Runtime
- Docker 20.10+
The desktop app starts Neo4j and Meilisearch in Docker for you. With the command line, one compose command does it: follow the quickstart.
Install
From download to first launch
No terminal needed. You install two helpers first, then the app does the rest. Allow a few minutes: the first start downloads what it runs on.
macOS
macOS 10.15 or later. Apple Silicon (M1 and later) or Intel.
What you need first
Tick what you already have; the steps below adapt.
Docker Desktop Required
It runs the database and the search engine the app depends on. The app starts them for you.
Claude Code For the chat
Needed for the chat assistant, and the setup waits for it. The app can install it for you during the Chat AI part of the setup. The AI itself is not provided by Project Orchestrator.
Step 1: Install and start Docker Desktop
Download Docker Desktop from Docker’s page, open the file, drag Docker to Applications, then open it and wait until it says it is running.
What you should see. Docker Desktop is open and reports that it is running. It is Docker’s own screen, so it is not reproduced here. Step 2: Download Project Orchestrator
Pick the file that matches your Mac. Not sure which? Open the Apple menu, choose “About This Mac”: a chip named M1, M2, M3 or M4 means Apple Silicon; anything mentioning Intel means Intel.
- Download .dmg
macOS, Apple Silicon
M1 and later · 46 MB
- Download .dmg
macOS, Intel
Intel Macs · 53 MB
What you should see. The .dmg file appears in your Downloads. Step 3: Open the app
Open the .dmg, drag Project Orchestrator to Applications, then open it from there. If macOS says it cannot check the app, we could not verify how the build is signed: allow it in System Settings, Privacy & Security, with “Open Anyway”.
What you should see. A start screen lists what the app checks. On the very first launch the Docker lines say “Setup pending”. Step 4: Setup 1 of 4: Infrastructure
Keep “Docker (recommended)”. The app looks for Docker Desktop. When it says “Docker Desktop is running”, press Next. If it says Docker is missing or not running, use the button next to the message, then wait: the app checks again by itself.
The services use the local ports 7474, 7687, 7700 and 4222, and the app itself uses 6600.
What you should see. A green line says “Docker Desktop is running” under two cards, “Docker (recommended)” selected. Step 5: Setup 2 of 4: Authentication
On a computer only you use, keep “No authentication” and press Next. On a shared or public network, choose “Password” and set an email and a password: without sign-in, the app’s server accepts connections from your whole network.
What you should see. Three choices (No authentication, Password, OIDC / OAuth), the first one selected. Step 6: Setup 3 of 4: Chat AI
If “Claude Code CLI is required” is shown, press “Install Claude Code CLI”. Then let the app download the search model when it offers to; the size is shown on screen. Next unlocks when both are ready.
If you have not signed in to Claude yet, see “If it does not work” below.
What you should see. Claude Code CLI shows a green check once installed (until then: “Claude Code CLI is required” and an install button), and the search model is marked ready. Step 7: Setup 4 of 4: Launch
Press “Generate Config & Save”. When “Configuration saved!” appears, press “Restart Application”. A switch on this screen controls whether the app checks for updates at start-up.
What you should see. A green “Configuration saved!” message and a “Restart Application” button. Step 8: Wait for the first start
On this second start the app downloads the three images it runs on, then starts them. The first time can take several minutes depending on your connection; later starts reuse the images and are quicker. When every line is green, the main window opens.
If a line says “Taking longer than expected”, wait. If a “Continue anyway” button appears, see “If it does not work”.
What you should see. A checklist (Docker Desktop, Neo4j, Meilisearch, NATS, Backend server) turning green one line at a time.
If it does not work
The three problems you are most likely to meet, with what the app shows.
Docker is not running
What you see. The app says “Docker Desktop is not running” or “Docker Desktop is required”.
What to do.
- Open Docker from your Applications folder (the app’s own Open button does the same). Wait until Docker says it is running.
- Come back to Project Orchestrator: it checks again every few seconds, for about two minutes. After that, quit and reopen the app.
A port is already in use
What you see. Neo4j or Meilisearch stays “Unhealthy”, or the app says it failed to start services. The services need the local ports 7474, 7687, 7700 and 4222.
What to do.
- Close the other program using that port: another database, search server, or an older copy of Project Orchestrator.
- Only the app’s own port (6600 by default) can be changed on the Infrastructure screen of the setup, “API Server Port”.
Only if you are comfortable with a terminal, this shows which program uses the port:
lsof -i :7687The chat cannot reach Claude
What you see. The setup says “Claude Code CLI is required”, or the chat says it has no Claude login.
What to do.
- On the Chat AI screen of the setup, press “Install Claude Code CLI” (or “Retry Install”).
- If the chat then asks for a login, open the Terminal app, type the command below, press Enter and sign in to Claude.
Type this and press Enter:
claudeWindows
Windows, 64-bit.
What you need first
Tick what you already have; the steps below adapt.
Docker Desktop Required
It runs the database and the search engine the app depends on. The app starts them for you.
Claude Code For the chat
Needed for the chat assistant, and the setup waits for it. The app can install it for you during the Chat AI part of the setup. The AI itself is not provided by Project Orchestrator.
Step 1: Install and start Docker Desktop
Download Docker Desktop from Docker’s page, run the installer, then start Docker Desktop from the Start menu and wait until it says it is running.
What you should see. Docker Desktop is open and reports that it is running. It is Docker’s own screen, so it is not reproduced here. Step 2: Download Project Orchestrator
Take the installer (.exe). The .msi file is meant for computers managed by an IT team.
- Download .exe
Windows, installer
64-bit, setup wizard · 61 MB
- Download .msi
Windows, MSI
64-bit, for managed deployments · 80 MB
What you should see. The .exe file appears in your Downloads. Step 3: Open the app
Run the installer and follow the wizard, then start Project Orchestrator from the Start menu. Windows may show “Windows protected your PC” because no signing certificate is set in the build configuration: choose “More info”, then “Run anyway” if you trust the download.
What you should see. A start screen lists what the app checks. On the very first launch the Docker lines say “Setup pending”. Step 4: Setup 1 of 4: Infrastructure
Keep “Docker (recommended)”. The app looks for Docker Desktop. When it says “Docker Desktop is running”, press Next. If it says Docker is missing or not running, use the button next to the message, then wait: the app checks again by itself.
The services use the local ports 7474, 7687, 7700 and 4222, and the app itself uses 6600.
What you should see. A green line says “Docker Desktop is running” under two cards, “Docker (recommended)” selected. Step 5: Setup 2 of 4: Authentication
On a computer only you use, keep “No authentication” and press Next. On a shared or public network, choose “Password” and set an email and a password: without sign-in, the app’s server accepts connections from your whole network.
What you should see. Three choices (No authentication, Password, OIDC / OAuth), the first one selected. Step 6: Setup 3 of 4: Chat AI
If “Claude Code CLI is required” is shown, press “Install Claude Code CLI”. Then let the app download the search model when it offers to; the size is shown on screen. Next unlocks when both are ready.
If you have not signed in to Claude yet, see “If it does not work” below.
What you should see. Claude Code CLI shows a green check once installed (until then: “Claude Code CLI is required” and an install button), and the search model is marked ready. Step 7: Setup 4 of 4: Launch
Press “Generate Config & Save”. When “Configuration saved!” appears, press “Restart Application”. A switch on this screen controls whether the app checks for updates at start-up.
What you should see. A green “Configuration saved!” message and a “Restart Application” button. Step 8: Wait for the first start
On this second start the app downloads the three images it runs on, then starts them. The first time can take several minutes depending on your connection; later starts reuse the images and are quicker. When every line is green, the main window opens.
If a line says “Taking longer than expected”, wait. If a “Continue anyway” button appears, see “If it does not work”.
What you should see. A checklist (Docker Desktop, Neo4j, Meilisearch, NATS, Backend server) turning green one line at a time.
If it does not work
The three problems you are most likely to meet, with what the app shows.
Docker is not running
What you see. The app says “Docker Desktop is not running” or “Docker Desktop is required”.
What to do.
- Start Docker Desktop from the Start menu (the app’s own Open button does the same). Wait until Docker says it is running.
- Come back to Project Orchestrator: it checks again every few seconds, for about two minutes. After that, close and reopen the app.
A port is already in use
What you see. Neo4j or Meilisearch stays “Unhealthy”, or the app says it failed to start services. The services need the local ports 7474, 7687, 7700 and 4222.
What to do.
- Close the other program using that port: another database, search server, or an older copy of Project Orchestrator.
- Only the app’s own port (6600 by default) can be changed on the Infrastructure screen of the setup, “API Server Port”.
Only if you are comfortable with a terminal, this shows which program uses the port:
netstat -ano | findstr :7687The chat cannot reach Claude
What you see. The setup says “Claude Code CLI is required”, or the chat says it has no Claude login.
What to do.
- On the Chat AI screen of the setup, press “Install Claude Code CLI” (or “Retry Install”).
- If the chat then asks for a login, open PowerShell, type the command below, press Enter and sign in to Claude.
Type this and press Enter:
claudeLinux
AppImage for Intel/AMD; .deb and .rpm packages for Intel/AMD and ARM64.
What you need first
Tick what you already have; the steps below adapt.
Docker Desktop Required
It runs the database and the search engine the app depends on. The app starts them for you.
Claude Code For the chat
Needed for the chat assistant, and the setup waits for it. The app can install it for you during the Chat AI part of the setup. The AI itself is not provided by Project Orchestrator.
Step 1: Install and start Docker Desktop
Follow Docker’s page for your distribution, then start Docker and wait until it says it is running. The app also recognises Docker installed without the Desktop application.
What you should see. Docker is running. It is Docker’s own screen, so it is not reproduced here. Step 2: Download Project Orchestrator
The AppImage runs on any distribution. Use the .deb on Debian and Ubuntu, the .rpm on Fedora and RHEL.
- Download .AppImage
Linux, AppImage
x86_64, runs on any distribution · 132 MB
Other versions for this system
- Download .deb
Debian and Ubuntu, x86_64
dpkg or apt · 61 MB
- Download .deb
Debian and Ubuntu, arm64
dpkg or apt, ARM64 machines · 55 MB
- Download .rpm
Fedora and RHEL, x86_64
dnf or rpm · 38 MB
- Download .rpm
Fedora and RHEL, arm64
dnf or rpm, ARM64 machines · 32 MB
What you should see. The file appears in your Downloads. Step 3: Open the app
For the AppImage: in your file manager, open the file’s properties and allow it to run as a program, then double-click it. For a .deb or .rpm: open it with your software installer, then start Project Orchestrator from your applications menu.
What you should see. A start screen lists what the app checks. On the very first launch the Docker lines say “Setup pending”. Step 4: Setup 1 of 4: Infrastructure
Keep “Docker (recommended)”. The app looks for Docker Desktop. When it says “Docker Desktop is running”, press Next. If it says Docker is missing or not running, use the button next to the message, then wait: the app checks again by itself.
The services use the local ports 7474, 7687, 7700 and 4222, and the app itself uses 6600.
What you should see. A green line says “Docker Desktop is running” under two cards, “Docker (recommended)” selected. Step 5: Setup 2 of 4: Authentication
On a computer only you use, keep “No authentication” and press Next. On a shared or public network, choose “Password” and set an email and a password: without sign-in, the app’s server accepts connections from your whole network.
What you should see. Three choices (No authentication, Password, OIDC / OAuth), the first one selected. Step 6: Setup 3 of 4: Chat AI
If “Claude Code CLI is required” is shown, press “Install Claude Code CLI”. Then let the app download the search model when it offers to; the size is shown on screen. Next unlocks when both are ready.
If you have not signed in to Claude yet, see “If it does not work” below.
What you should see. Claude Code CLI shows a green check once installed (until then: “Claude Code CLI is required” and an install button), and the search model is marked ready. Step 7: Setup 4 of 4: Launch
Press “Generate Config & Save”. When “Configuration saved!” appears, press “Restart Application”. A switch on this screen controls whether the app checks for updates at start-up.
What you should see. A green “Configuration saved!” message and a “Restart Application” button. Step 8: Wait for the first start
On this second start the app downloads the three images it runs on, then starts them. The first time can take several minutes depending on your connection; later starts reuse the images and are quicker. When every line is green, the main window opens.
If a line says “Taking longer than expected”, wait. If a “Continue anyway” button appears, see “If it does not work”.
What you should see. A checklist (Docker Desktop, Neo4j, Meilisearch, NATS, Backend server) turning green one line at a time.
If it does not work
The three problems you are most likely to meet, with what the app shows.
Docker is not running
What you see. The app says “Docker Desktop is not running” or “Docker Desktop is required”.
What to do.
- Start Docker Desktop, or your Docker service if you use Docker without the Desktop application. The app’s Open button only tries to start Docker Desktop.
- Come back to Project Orchestrator: it checks again every few seconds, for about two minutes. After that, close and reopen the app.
A port is already in use
What you see. Neo4j or Meilisearch stays “Unhealthy”, or the app says it failed to start services. The services need the local ports 7474, 7687, 7700 and 4222.
What to do.
- Close the other program using that port: another database, search server, or an older copy of Project Orchestrator.
- Only the app’s own port (6600 by default) can be changed on the Infrastructure screen of the setup, “API Server Port”.
Only if you are comfortable with a terminal, this shows which program uses the port:
lsof -i :7687The chat cannot reach Claude
What you see. The setup says “Claude Code CLI is required”, or the chat says it has no Claude login.
What to do.
- On the Chat AI screen of the setup, press “Install Claude Code CLI” (or “Retry Install”).
- If the chat then asks for a login, open a terminal, type the command below, press Enter and sign in to Claude.
Type this and press Enter:
claudeQuestions
Before you install
Short answers, each one checked against the source code of the app.
Is it free?
Yes. The download has no price and the source code is public on GitHub.
The one cost that can exist sits outside the app: the chat assistant runs through Claude Code, which you install separately and which follows the plans and terms of Anthropic.
Where does my data go?
Your plans, tasks, notes and decisions stay on your computer, in a database and a search engine that the app starts for you. They only accept connections from your own machine.
Chat is the part that talks to the outside: what you type, and what the assistant reads to answer you, is sent to Claude by Claude Code, under the terms of Anthropic.
Search by meaning runs on your computer (its model is downloaded once). The app checks GitHub for new versions when it starts. No analytics or tracking code was found in the source.
Do I need an account?
No account with Project Orchestrator: there is nothing to sign up for, and the setup uses no sign-in by default.
You can add a password, or sign-in with Google, Microsoft or another OpenID provider, during setup.
Good to know: with no sign-in, the app’s own server accepts connections from your whole network, not only from your computer. On a shared network, choose a password.
Do I have to install Docker?
Yes, by default. The app keeps your data in a database and a search engine, and it runs them with Docker Desktop. You install Docker Desktop once; the app then starts and stops those services itself.
The setup checks for Docker, tells you if it is missing or not started, and does not let you continue until it runs.
People who already run their own database and search servers can point the app at them instead (the “External servers” choice in the setup).
Is the AI included, or do I need my own subscription or key?
The AI is not included. The chat assistant works through Claude Code, Anthropic’s tool, which has to be on your computer and signed in to your Claude account. The setup can install it for you.
To sign in you may have to type claude once in a terminal; the app’s own message says so. No key is asked for in the setup.
Which plan Claude Code requires is decided by Anthropic, so check their site. The setup will not let you finish until Claude Code is detected.
Can I use it without writing code?
For daily use, yes: you work in the app (Today, plans, tasks, notes, decisions) and ask the assistant in a chat. The installation does not need a terminal either, apart from the possible one-time Claude sign-in.
A project does not have to be software: recent versions support projects without a code folder.
The honest limit: the product started with developers, and some screens still lean that way, for example the starter suggestions of the chat (impact analysis, code search, architecture).
Which computers does it run on?
macOS 10.15 or later (Apple Silicon and Intel), Windows 64-bit, and Linux (an AppImage for Intel/AMD machines, .deb and .rpm packages for Intel/AMD and ARM64).
Docker Desktop has to run on the same computer. There is no phone app and no hosted web version: the downloads on the release page are all desktop packages.
How do I update it?
The desktop app checks for a new version each time it starts and shows a banner when one is ready. You can switch this off in the last step of the setup.
If no banner shows up, download the latest installer from the release page and run it.
Can I use it with my team?
Not as a shared team space yet: today each person runs their own Project Orchestrator.
What exists: workspaces, to group several of your projects, and an early version of sharing between two instances. You decide, per project, whether notes are shared manually, suggested to you, or sent automatically; copies can expire, and you can withdraw a share.
What is planned and not available: one common knowledge base for a company, teams and hierarchy, roles and access rights.
Which licence is it under?
Two licences, as the LICENSE file states (copyright FFS SAS): MIT AND BUSL-1.1.
The parts under the MIT licence can be used, copied, modified and shared freely.
The part marked Enterprise Edition is under the Business Source License 1.1: you may test, develop and evaluate with it, but using it in production needs a commercial licence from FFS SAS (contact@ffs.holdings). That part becomes MIT four years after publication.
What happens when I close the window?
Closing the window hides the app in the system tray; it keeps running. Choose Quit from the tray icon to stop it.
Quitting also stops the three services the app started in Docker (database, search, events). If you use your own servers, it leaves them alone.
How do I get help or contribute?
Join the Discord to ask for help or give feedback. For a bug, open an issue on GitHub and include your system, the steps to reproduce it and any error message.
Contributions are welcome. The contributing guide explains how to set up the project and what a good report contains; it is written for developers.
Get started
Give your agents a memory and a plan
Install the orchestrator, connect Claude Code over MCP, and let your first agent read the project before it writes a line.
Or start from the terminal
brew install this-rs/tap/project-orchestrator