Shed in production
A small team ships faster when nothing between the code and the internet needs owning. Shed gives you machines, not a platform: each one has a domain, HTTPS and SSH from the second it exists, and you decide who can open it.
The whole stack, named
One machine for the app, one for the database, one for the worker that drains the queue. Each has its own address, so nothing is a path on somebody else's host, and any of them can be reached over SSH when something needs looking at.
There is no build system to satisfy and no manifest to keep current. A machine runs what you install on it.
Staging is a fork
Copy a running machine, filesystem intact, and you have the same data and the same software at a different address. Try the migration there. Delete it when you know.
That is the whole staging story: no second environment to provision and keep in step, because the copy started as the thing it is testing.
Sharing is by person
Machines are private. You share one by naming someone, and they sign in as themselves. Holding the URL grants nothing, so a link in a Slack channel is not an outage waiting to happen.
When someone leaves, you unname them. There is no shared password that has to be rotated.
Machines you would make
app: the product your customers usepostgres: the database it talks toapp-staging: a fork of app, disk and all
Join the waitlist
Shed is not open yet. The other two use cases are sandbox and vps.