The app works. Now get it into their hands.
You've built something real. The last mile — a URL, a login, a database that isn't on your laptop — is where most projects stop. That's the part shovelbase already did.
Where it stops
Running on your machine isn't shipped.
Your agent can write the app. What it can't hand you is somewhere for it to live. Every guide from here turns into a tour of things you didn't set out to learn — containers, DNS records, IAM policies, a database you have to run — and the app that worked twenty minutes ago is still only working for you.
What that looks like here.
You don't need to know what a container or a load balancer is. Your agent drives the CLI, and the infrastructure underneath is already standing.
Publish and it's live at its own URL. The people you built it for open it in a browser — nobody clones a repo or installs anything.
Sign-up, sessions, invites, password resets and the emails that carry them are wired from the first day. It's the part that stops most first projects.
How it goes.
- 1Point your agent at shovelbase
Install the CLI or connect over MCP. Claude Code, Cursor, or whatever you already use takes it from there.
- 2Say what the app needs
Your agent creates the project and sets up auth, the database, storage, and functions — no console clicking.
- 3Publish it
One command puts the app on a global CDN at its own address, with HTTPS handled for you.
- 4Send the link
They open it, sign in, and start using it. That's the whole handoff.
What you'll use most
The distance between “it works on my machine” and “my friends are using it” should be one command. Here it is.