the deal, in plain words

1. who you are dealing with

switchyard is made by one founder in the united kingdom and is being set up as a company. until registration completes, your agreement is with the founder trading as switchyard; this page will name the company when it exists, and your agreement will pass to it with no other change. contact: hello@switchyard.so.

2. what the service is

switchyard gives each coding agent its own task on a copy of your repository, warns when work overlaps, runs your checks, suggests fixes for conflicts, and merges what passes onto your main branch, on github or in switchyard's own storage. what it does today is described in the docs; what it promises about your data is on the guarantees page. where the docs and these terms differ, these terms win on the legal points and the docs on how things work.

3. the private beta

the service is in private beta. we invite teams a few at a time, we change things often, and some parts are new. we will tell you before a change that removes something you use. nothing in the beta is a promise about what the service will do later.

4. your account and your team

• you sign in with github and are responsible for what is done with your account and with the keys your team creates for its agents. keep them private and rotate one that leaks.
• an owner or admin of a team may add and remove people, connect repositories, turn AI suggestions on or off, set test secrets, and delete projects. these actions are written to the team's audit log.
• you must be at least 16 and use the service for work, not for anything unlawful, and not to attack, scan or overload it or anyone else.

5. your code stays yours

you keep every right in your repositories, your agents' work, your plans and your conflict fixes. you give us only the permission we need to run the service for you: to store your git data, run your checks, show your team its work, send conflicts to the AI when your team has turned that on, and merge to the branches you point us at. we do not train models on your code, and we do not read it except to fix a problem you asked us to fix, which is recorded in your audit log. you confirm you have the right to connect the repositories you connect.

6. checks, agents and AI suggestions

• a check runs your code and your tests in a container we start for it. what the code can do there, it does; keep production credentials out of test secrets. a check's result decides whether a change merges, under the rules your team sets.
• an AI suggestion is a suggestion. it changes nothing until a person or the task's agent accepts it, and the checks still run on it. you are responsible for what you accept.
• agents act with the keys you give them. what an agent does on a task is yours, as if a member of your team had done it.

7. fees

• the pricing page is part of these terms. during the private beta nothing is charged; billing for your team starts on the day we tell you, and the first month's minimum is pro-rated from that day.
• each plan has a monthly minimum. usage counts against it at the published rates, and the month's bill is the larger of the two, charged in arrears. unused minimum does not roll over.
• prices are in us dollars and exclude vat and sales tax, which are added where they apply. we may change prices with 30 days' notice by email to your team's owners; a change never applies to a month that has started.
• if a payment fails, we tell you and try again. after 14 days unpaid, new merges and checks pause until it is settled; your data is kept and nothing is deleted for that reason. after 60 days unpaid we may close the team's projects under section 10.

8. what we promise about availability

we run the service with care and tell you plainly when something is wrong, but on the launch and scale plans we do not promise a level of uptime, and the service is provided as it is. an uptime commitment and a support commitment are available by contract on the enterprise plan. we are not responsible for github, cloudflare or anthropic being unavailable; when github is down, your pushes to switchyard keep working and merges to github wait and land when it is back.

9. your data

the privacy policy says what we collect and how long we keep it. our data promises, which we treat as the first rule of the product, are on the guarantees page: nothing you send is lost, every change is recorded, and a conflict never deletes work. a data processing agreement is available on request to paying teams.

10. leaving, and closing

• you can stop any time. your code is plain git: clone it and it is yours in full. you can delete your projects and your account from the product.
• a deleted project is kept 30 days so a mistake can be undone, then purged. after that, we cannot recover it.
• we may close a team's projects for serious or repeated breach of these terms, for non-payment under section 7, or if we stop offering the service, with 30 days' notice in the last case and your data available to take for those 30 days.

11. responsibility

to the extent the law allows: we are responsible to you for the fees you paid us in the 12 months before the event, and not for lost profit, lost data you could have cloned, or indirect loss. nothing in these terms limits what the law does not allow us to limit, including liability for fraud or for death or injury caused by negligence. you are responsible for the code your agents and people push, and for having the rights to it.

12. the law that applies

these terms are governed by the law of england and wales, and disputes go to its courts, unless you are a consumer with a right to your own country's courts. if a part of these terms cannot be enforced, the rest stands.

13. changes

when these terms change, the date at the top changes and we say what moved. for a change that reduces what you get, we email your team's owners 30 days before it applies. using the service after that date accepts the change.