Shed

Deploy any code your agent ships.

Your agent writes the code. The Shed CLI deploys it.

What you install.

Two pieces, installed separately. The CLI deploys. The skill teaches your agent to drive it. Neither is open yet.

Setup guides, agent by agent

The CLIsoon

Required

Packages your project, builds it on Shed, returns a live URL.

The agent skillsoon

Optional

Teaches Claude Code, Cursor, and Codex to write a SHED file and run the CLI.

MCP

Not built yet

A server your agent connects to instead of running the CLI.

Every host can run it. Count what it costs to get there.

Measured in handoffs, not minutes: the moments the agent stops and waits for you to open something. They are what actually make setup feel long.

  1. Google Cloud RunBilling and three APIs before the first deploy.
    1. create a Google account
    2. create a Cloud project
    3. attach a billing account
    4. install the gcloud CLI
    5. gcloud auth login opens a browser
    6. set the active project
    7. enable the Cloud Run API
    8. enable the Cloud Build API
    9. enable Artifact Registry
    10. answer the region and access prompts
    11. deploy

    9handoffs

  2. VercelBuilt around a Git connection and a framework preset.
    1. create an account
    2. install the CLI
    3. vercel login
    4. link or create the project
    5. confirm the framework preset
    6. deploy

    4handoffs

  3. RailwayThe deploy succeeds and nothing is reachable yet.
    1. create an account
    2. install the CLI
    3. railway login
    4. answer the railway init prompts
    5. railway up
    6. generate a domain in the dashboard

    4handoffs

  4. Fly.ioOne launch command, but it interviews you.
    1. create an account
    2. install flyctl
    3. fly auth login
    4. add a payment method
    5. answer the launch prompts
    6. deploy

    4handoffs

  5. Cloudflare WorkersNo billing form, but the scaffold interviews you.
    1. create a Cloudflare account
    2. install the Wrangler CLI
    3. answer the create-cloudflare prompts
    4. wrangler login opens a browser
    5. deploy, claiming a workers.dev subdomain

    3handoffs

  6. ShedSign in once, then it is one file and two commands.
    1. create an account
    2. install the CLI
    3. shed login, approve in the browser
    4. shed init writes the SHED file
    5. shed deploy returns a URL

    2handoffs

the agent can do it from the shell you have to go somewhere else

What you get, and what is coming.

Today

  • Deploy from the CLIThe build runs on Shed, not on your laptop.
  • Build and runtime logsStreamed live, or read after the fact.
  • Status and historyEvery deployment and what happened to it.
  • Cancel and retryStop a bad deploy before it replaces what is live.
  • Scale to zeroIdle deployments cost nothing to keep around.
  • Sandboxed by defaultA gVisor sandbox on a tenant-only node pool.

Next

  • Private sharingsoonName the people who can open it. Nobody else can.
  • Auth in front of your appsoonSign-in you do not have to build.
  • Jobs and cronsoonRun it once, or on a schedule, and keep the exit code.
  • More than one servicesoonSeveral pieces in one deployment, talking to each other.
  • MonitoringsoonRequests, errors and latency without wiring anything up.
  • AlertssoonTell you it broke before someone else does.

Before you hand it off.

What can I deploy with Shed?+

Web applications, APIs, workers, scheduled jobs, one-off scripts, or a container you bring yourself. Shed detects what the project needs and runs it.

Which coding agents work with Shed?+

Any agent that can run the Shed CLI. We ship a skill for Claude Code, Cursor, and Codex so they already know how.

How does Shed build and deploy my project?+

Shed builds from what is declared in the SHED file. Nothing outside it gets picked up: no ambient laptop state, no hidden dependencies.

Are deployments isolated?+

Yes. Each deployment runs in a gVisor sandbox on a node pool reserved for tenant workloads, so the kernel your code calls into is not the host's. Nothing shares a process tree with anything else you're running.

How does scaling work?+

A Shed scales to zero when idle and back up when a request arrives. The bounds are set by us for now; per-project limits are not exposed yet.

Why not Railway or Fly.io?+

Their unit is a project you tend: name it, add services, expose it in a second step. Agents produce software nobody tends, in volume. Different unit, not a worse cloud. Railway is a canvas.

Why not Vercel or Cloudflare?+

Vercel starts from a repository and a framework it recognises; an agent has a folder and twenty minutes. Cloudflare has every piece, and expects you to assemble them. Vercel is a workflow, Cloudflare is a kit of parts.

Where does my code run?+

Managed Kubernetes on GCP and AWS, each deployment in its own sandbox. Low-cost data centres are planned next, so idle software costs less to keep alive.

What do I get when a deployment finishes?+

Your agent receives a live URL in the same session. shed logs <id> streams stdout and stderr from any run.

Give your agents somewhere to build.