Tares for Software Factory

A software factory is a crew of Claude Code sessions that builds software the way a small team does. You agree on a plan, the crew hands out the work, builders open pull requests, a reviewer holds every change to a fixed bar, and a change merges once it passes review and CI. Tares holds the plan, the tickets, every review and every decision, so the crew carries on across restarts and you can check each choice it made.

You plan a project once, in Claude Code, and get it back merged. You are pulled in only for the decisions that are yours.

The crew

The crew runs in the background on your machine, on your own Claude Code login.

• Orchestrator: hands out work, answers the other sessions, and brings you what needs you. It is the one session you talk to.
• Reviewer: reviews every pull request to a fixed bar and posts its verdict on it.
• Builders: one per milestone and repo of a project, started by the orchestrator. Each takes a ticket, works on its own branch, opens a pull request and merges it once the reviewer passes it and CI is green.
• Releaser: only if you ask for one. It tags and deploys. Without it, work ends merged on main.

One crew serves every project you hand it, side by side. While one project waits for you, the others carry on.

How a project moves

1. Plan. tares factory spec "what you want to build" opens Claude Code, which interviews you, has a second model attack the plan, and writes a spec, milestones with acceptance checks and tickets into Tares. Plan a project
2. Build. The orchestrator starts builders. Each ticket becomes a branch and a pull request. Run the crew
3. Review. The reviewer checks every pull request, and the builder fixes what it asks for. Pull requests that wait for your merge show on the Reviews page.
4. Decide. Questions reach you one at a time, each with a recommendation. Choices the crew made on its own (its calls) come to you once per milestone.
5. Done. When the last milestone’s checks pass, the project is ready to close, every ticket merged.

The console shows all of it: what waits for you, each project’s progress, the tickets, the pull requests in review and the crew at work.

Where Tares runs

The crew always runs on your machine. Tares, which keeps the record, runs either:

• on Tares Cloud: create a Software Factory workspace and sign in with tares login. Nothing to host, and team features are included.
• on your local machine: tares up, the same open source Tares. A team on one self-hosted Tares needs an enterprise licence.

Install and run covers both.

For one developer or a team

On your own, the factory takes whole projects off your hands while you work on something else.

With a team, everyone on the same Tares runs their own crew. A project has a lead, a repo has an owner, the spec asks the owner of a repo instead of guessing, and every ticket, review and decision records the person behind it. Teams

Start here