Switchyard
A self-hosted Git collaboration platform where humans and coding agents work concurrently on real repositories without turning canonical branches into last-writer-wins shared state.
Git hosting that treats concurrent agents as first-class collaborators.
Switchyard keeps ordinary Git at the center of the product. Repositories, branches, commits and canonical history live in real Git hosted by Cloudflare Artifacts; normal git clone, fetch and push workflows continue to work. Switchyard adds the coordination layer around that Git state rather than replacing it with a proprietary source-control model.
Work records intent, Attempts isolate competing implementations, Pull Requests collect review and validation, and the Integration Queue serializes canonical changes through checks, policy and compare-and-swap ref updates. Humans and agents can therefore work in parallel without giving every actor direct write access to main.
That same model supports durable programmable workflows, structured review findings, semantic conflict checks, provenance and a Needs Attention inbox for decisions that automation cannot safely make alone. A conventional human-only repository still behaves like a familiar Git host; the agent-native machinery appears progressively when the workflow needs it.
Familiar Git collaboration with a concurrency layer built for agents.
The common case stays recognizable; advanced coordination becomes available without forcing every repository into an orchestration-heavy workflow.
Cloudflare Artifacts is the authoritative remote Git host, so branches, commits, refs, clone/fetch/push and canonical history remain ordinary Git.
Record intent once, then let humans or agents try isolated implementations without sharing one mutable working branch.
Preview, checks, policy, semantic validation and the Integration Queue decide what may move canonical instead of relying on force-push or last-writer-wins behavior.
JavaScript-authored workflows coordinate Agent runs, checks, review, repair, approval and integration with replay-safe durable step boundaries.
From intent to canonical Git without losing parallel work.
Switchyard uses established Git concepts for the repository and introduces new concepts only where concurrent autonomous work needs them.
- 01
Create a Work item for the feature, fix or maintenance task. A normal human-only workflow can stay here until somebody starts implementation.
- 02
Create one or more Attempts. Each gets isolated Git state, so a human and several agents can explore different solutions without overwriting one another.
- 03
Open a Pull Request, run checks and reviews, and preview the candidate against the current canonical branch. Textual and contract-level semantic conflicts become findings instead of surprises after merge.
- 04
Queue an approved candidate. The Integration Queue revalidates it against the latest canonical state and performs the real Git integration only when checks, policy and freshness still hold.
Dogfooding the stack at the collaboration layer.
Switchyard is useful as its own Git product, while several Gantry projects provide deliberately separated parts of the implementation.
Nift
Nift builds the brochure and application shell as ordinary web assets. The UI stays separate from the Go control plane and can use Nift's dependency-aware build model without introducing a frontend framework runtime.
Explore Nift →Trestle
Trestle is Switchyard's durable coordination truth: Work, Attempts, workflow state, findings, queue state, policies, audit records and other application state live there while Git itself remains authoritative in Artifacts.
Explore Trestle →Strut
Switchyard's bounded deterministic worker uses Strut behind the runner abstraction. That executor layer keeps disposable task execution separate from the Go control plane and durable coordination state.
Explore Strut →Warden
Warden is the self-hosted coding workspace; Switchyard is the Git collaboration and integration layer around repositories. A developer can edit in Warden while Switchyard coordinates branches, review and concurrent Agent work.
Explore Warden →Use normal Git clients and the Switchyard web app together.
Git commands talk directly to the Cloudflare Artifacts remote. Switchyard obtains short-lived repo-scoped credentials and wraps the collaboration policy around those repositories; it does not proxy every Git object through its own database.
The web application adds repository browsing, profiles, Work, Pull Requests, workflows, review, editor/Agent assistance, Integration Queue state and Needs Attention. Self-hosted deployments can sit behind a normal TLS reverse proxy while Trestle and the control plane's internal ports remain private.
See how Switchyard works →Where Switchyard earns its place.
Let several agents attempt work simultaneously while preserving isolated branches, provenance and deterministic canonical integration.
Keep ordinary Git, PRs and review familiar while allowing agents to implement, review or repair within explicit roles and policies.
Run the collaboration control plane yourself while keeping repository truth in real Git rather than a custom source-control database.
Explore Switchyard.
Architecture, product walkthroughs, documentation and setup guidance live on the Switchyard project site.