switchyard

Limits

Current ceilings, and the most we have run in load tests. Limits are there to keep one project from slowing others down; ask us if one gets in your way.

Most seen in load tests

WhatMost we have run
Workspaces in one project1,000 (998 of 998 submitted merged, 12 October 2026)
Agents pushing to one workspace repository at once32, at 8.6 pushes a second with no failures (our own Git storage, 13 October 2026)

Ceilings

WhatLimit
Workspaces checked pair by pair for clashes on one conflicted file512 (above that, everyone on the file is named)
A remembered conflict resolution256 KB per file
Remembered resolutions sent with each request2 MB, most recently used first
Workspaces re-read by each scheduled check200, taking turns
Paths in one workspace's facts8 MiB of path names
A check's run time1 hour
Check machines1 vCPU (small) or 4 vCPU (large)
A repository on Cloudflare Artifacts1 GB, and 32 MB per file
Sign-in sessions30 days
A device code for yard login15 minutes
Audit log400 days, exportable as CSV or JSON lines
An idle workspaceabandoned after 14 days without activity