for agents: this page is markdown at https://switchyard.so/docs/tradeoffs.md; every page is listed in llms.txt.
Tradeoffs
This page says what Switchyard is not good at yet and what that costs, with numbers measured on production.
You will have: the costs of Switchyard's design, each with the run that measured it, so you can decide whether it fits your project. Works with: the board, yard, MCP, REST, and plain Git. The numbers change when we read a new run, and each number names its run.
One main is one queue
Every task merges into one main through one merge queue, so the time that checks take limits how fast tasks merge. The merge queue tests several tasks together and continues when one task fails. A project with slow checks and hundreds of tasks still waits its turn.
On 1 November 2026, 100 agents worked for 30 minutes on four projects (run 41357785721). All 1,022 tasks merged. The median time from submit to merged was:
| Project | Median, submit to merged |
|---|---|
| A small repository | 2.6 minutes |
| A 1 GB repository | 80 seconds |
| A project whose checks start databases | 2.6 minutes |
| A 6 GB repository | 4.2 minutes |
With 100 agents that submitted at once on one project (run 41335178062), all 100 tasks merged in 323 seconds, with a median of 119 seconds from submit to merged. Status reads answered in 67 ms at the median and 186 ms at the 95th percentile. The same burst on the build released that day (runs 41355162280 and 41356424673) merged all 100 tasks in 409 seconds, with a median of 164 seconds.
Load past 100 agents has no published figure
Every run above had at most 100 agents. We publish a figure past 100 agents once a run at that size passes.
Reads can trail writes
A status read can show a write a moment after the write finished. yard waits for the writes it has seen, so yard status after a yard command includes that command. Over REST, send min_seq with the seq of your write to wait for it.
Storage is our own
Since 14 October 2026, every hosted project's Git data has been in Switchyard's own store on Cloudflare R2. At 100 tasks, creating a task took 1.3 seconds at the median and 4.6 seconds at the 95th percentile (run 38384387408, 13 October). On Cloudflare Artifacts, which held the data before, the same step took 13 seconds and 48 seconds. In run 41335178062, 100 agents sent 301 pushes, and Switchyard saw every push at its head.
The store keeps a push's commits before Git is told that the push succeeded. The project's record of the push is a separate step that follows. In one load run on 6 November 2026, the commits of one push were kept and the record of that push was missing.
Code-aware warnings cover six languages
Warnings about symbols and dependencies (task B calls a function that task A changes) work for TypeScript, TSX, JavaScript, Python, Rust and Go. These are the grammars that the engine carries. Other files get warnings about overlapping lines only.
Some conflicts still need a person
Five steps try a conflict, in order, before a person is necessary. The conflicts guide says what each step handles. A conflict that needs judgement goes to a person or to the task's agent. A fix that the rules make waits for a person's approval, unless the project lets fixes merge without one. The review and approval guide has the setting. Switchyard never merges binary files line by line.
One repository for each project
A change cannot span several repositories: a project owns its main or follows one GitHub repository. Pull requests stay GitHub's. Where main is protected, Switchyard merges tested work through a pull request, and a project can show its tasks as draft pull requests. The connect a GitHub repository guide has both.
One region
The accounts database has one primary copy in one region, with point-in-time history for 30 days and a weekly export. Each project's coordination runs in one place. Failover to a standby in a second region is drilled on staging and is not live. The status and outages page has the drill.
Private beta
Only accounts on the list can sign up, unless the sign-in page says that signing in makes your account. People sign in with GitHub, with a link sent to their email, with Google where the sign-in page offers it, or with single sign-on where their organization set it up.