Do I need a specific agent?
No. Bring Claude Code, Cursor, or whatever you use. Shed takes the output.
Shed cloud
A cloud for everything your agents build.
Give Shed the code. It runs in your team's environment and gives you a link. No deployment, configuration, or copied secrets.
Deploy this tool for the team.
I'll deploy customer-brief with the Northwind environment.
Thinking… checking the project and its environment
Running 1 tool…
$ shed build ./customer-brief --env northwind/production✓Reading project12 files
✓Detecting runtimeNode.js 22
✓Binding environment4 resources
✓Building servicecomplete
✓Starting instancehealthy
Deploying…
4.2sDone — it's live for your team.
shed.sh/northwind/customer-brief01 / Shedfile
One file between code and cloud.
Your agent generates a Shedfile from the project. It describes how the tool runs and which environment resources it needs. You don't write deployment config.
Make this deployable with Shed.
Created Shedfile from the project
Shedfilenew
01
service: web02
runtime: node@2203
start: pnpm start04
05
use:06
- customers-db07
- workspace-identity✓ Ready to deploy
02 / Isolation
Every tool gets its own boundary.
Each deployment runs separately and receives only the environment resources declared in its Shedfile. Small tools stay predictable instead of becoming tangled infrastructure.
customer-briefinvoice-reviewweekly-report
Isolated runtime
Node.js 22customer-brief
service: web HealthyDBcustomers-dbconnected
IDworkspace identityconnected
03 / Services
One format. Many kinds of software.
Web apps, APIs, workers, and scheduled jobs use the same small declaration. Your agent writes the right Shedfile for the project.
Use caseInternal dashboard
ReadyShedfile
01
service: web02
runtime: node@2203
start: pnpm start04
use: customers-dbQuestions
The short answers.
Why not Cloud Run or Workers?
Shed can run there. They provide the runtime; Shed provides the environment and sharing.
Does our code leave our network?
Only if you want. Point the environment at your own infrastructure.