About Shed

Shed is a cloud of persistent computers for people and coding agents. Each one is a virtual machine with root, its own disk, and an address that answers over HTTPS and accepts SSH. It keeps its files between sessions. The same CLI works for you and for the agent, so the session where tools such as Claude Code, Cursor, and Codex write and test code can also make the machine the code runs on.

Our mission

We are building a cloud where an agent can have a computer of its own. An agent can write a service, test it, and fix its own bug. Then it stops, because the next step is a browser. Removing that stop is the whole mission.

Making a computer should be as easy as creating a Google Doc: it exists, it has an address, and nothing had to be chosen first. Protecting it should be as easy as sharing one: private until you name someone, and then that person can open it and nobody else can.

What Shed is for

Shed is for small software: the tools, scripts, dashboards, and services that people and agents write in an afternoon and that sit idle most of their life. A Shed is made blank, with software already on it, or from a GitHub project, and the same computer is kept three ways: a sandbox for one job, a VPS that stays on, or production on machines you can name.

Company

Shed is operated by Local Group Software, Corp., a Delaware corporation. Local Group Software, Corp. is also the controller of personal data processed through Shed accounts, as set out in the privacy policy.

Company mailing address:

Local Group Software, Corp.
1968 S. Coast Highway, #3447
Laguna Beach, California 92651
United States

Contact

Email support@shed.codes for product support, account and billing questions, privacy requests, security reports, abuse reports, copyright notices, legal notices, or general business questions. It is the primary public address for Shed and reaches the team that routes each request.

Written legal notices may be sent to the company mailing address above. Do not email access tokens, private keys, source archives, .env files, or other credentials.

The contact page covers what to include in a technical support request. Product writing is on the blog, and we post as @ShedCloud on X. You can also read the terms of service and the acceptable use policy.