Conduit logoConduit

Conduit Yard

Coming soon

Write the job. We run it.

Yard runs custom jobs on the Hub graph, on a schedule. You write what to do. We host the sandbox: allowlisted tools, a budget, a step cap, no shell.

Assign an agent. You set autonomy level: notify, suggest, or act.

Conduit Hub

Running a job

Competitor Tracker

See the shape of it in Hub.

Custom jobs without a server.

You should not have to program, or host, to run a standing job. Write it in English. Yard runs it in a sandbox we operate: allowlisted tools, a budget, a hard step cap, no shell.

The job finishes quietly. You get a brief of what happened and what to do. Safe and predictable, still yours to customize.

Questions

What is Conduit Yard?
Yard runs custom jobs you write on the Hub graph, on a schedule. You write the job. We host the sandbox. Assign an agent; you set notify, suggest, or act.
Does Yard work with my ERP?
Yard runs on the Hub graph, not on a specific stack. Connector is how that graph is mapped from the system you already run.
Do I need to code or host a server?
No. Write the job in English. We run it: allowlisted tools, a budget, a step cap, no shell. You do not program, and you do not host.
Is Conduit Yard live yet?
Coming soon. Hub shows the shape of Automations today. Request a demo if you want a walkthrough.
Do Yard jobs buy on their own?
You define the autonomy level for every job, and permissions on the assigned agent, so nothing unexpected happens. The same job can just notify, suggest a fix in one click, or act automatically. Acting still needs checkout permission and an approved spend mandate.
Can I use my own agents?
Yes. Self-host your agents and use them in Hub flows over MCP.
How is Yard different from Pipes?
Pipes are seeded jobs: disruption brief, restock, price, and parcels. Yard is the custom job when your flow is not one of those.