Personal
$15 a month
One person and their agents.
$15 of machines included2 vCPU all month, any sizes
- any machine size
- SSH and an HTTPS address on every machine
- fork a machine, disk and all
- daily snapshots, kept 7 days
- email support
A shed is a computer in the cloud with its own disk, terminals and address. Give one to your coding agent, keep one as your dev machine, or make one for a job and throw it away.
01 — Teleport
Your working tree, your tools and your shell move to a shed in one command, and back. Teleport looks at what’s installed on your laptop and puts the same on the machine before you arrive.
shed teleport .
Shell reattached · ~/notes-app on upload-retries · 4 sBack on the laptop: shed teleport --home
02 — Sync
A folder on your laptop and the same folder on the shed, kept the same in both directions, .git included. Edit in your editor, let the agent edit on the shed; the other side has it.
laptop~/notes-app/src/upload.ts18:12:04.210
shed~/notes-app/src/upload.ts18:12:04.962
03 — Durable
An agent’s environment usually disappears when the session does. A shed keeps its own disk: the repo, the packages it installed and the branch it was on are there next time. It sleeps when idle and wakes when you connect.
18:12
asleep since · nothing lost
this week
Nightly snapshot · 7 kept · last today 03:00
Try it
An example account, live. Pick a machine, open a tab, or fork one from ⋯. Nothing you do here touches anyone’s real shed.
Add a description…
Ctrl+` new terminal · Ctrl+Shift+] next tab
An example account. Pick a machine, open a tab, or fork one from ⋯.
Claude Code, Codex and bash open as tabs. Close the browser; they keep running. Open it; they’re where you left them, or over SSH.
HTTPS from the first second, any port. Name the people who can open it; each signs in as themselves. The link alone opens nothing.
Fork a shed and get a second computer with the same disk, its own address and its own sessions, seconds later. The original is untouched.
Ask your agent for a machine, or deploy to one from GitHub Actions. Usage, processes and disk for each, at a glance.
Here’s the list. The long version →
| On a VPS, you | On a shed |
|---|---|
| Create SSH keys and open a port for them | SSH from the start |
| Install tmux, so the agent’s shell survives a disconnect | tmux, toggled on when you make it |
| Install the coding agent | Claude Code, Codex and OpenCode, toggled on at creation |
| Copy your project and reinstall your tools | shed teleport . |
| Point a domain at it and set up TLS | Its own HTTPS address from the start |
| Put a login in front of the preview | Name the people who can open it; they sign in as themselves |
| Snapshot it and build a second server to try an idea | Fork it, disk and all |
PRICING
Every plan runs every machine size. Its price is spent on your machines at one list price, and plans differ in what you can do with them.
Personal
$15 a month
One person and their agents.
$15 of machines included2 vCPU all month, any sizes
Pro
$40 a month
For work you share.
$40 of machines includedabout 5 vCPU all month, any sizes
Custom
Custom
Bigger fleets and your own terms.
Priced for your fleetvolume rates on every size
Every plan runs every size, and its price is spent on your machines at the list price. Past it, you pay the same list price, by the hour.
Shed isn’t open yet. Leave your email and we’ll tell you when it is. First 100 waitlist signups get one month of Personal free when Shed opens.
No card. No newsletter. One email when it opens.