Run

Ship a site in one command.

Publish a landing page, your docs, or a whole web app to a global CDN, straight from the CLI.

$ shovelbase sites publish
✓ published → https://<ref>.shovelbase.com
✓ CDN invalidated
One command

The CLI publishes and invalidates the CDN. No build pipeline to wire up.

Custom domains

Point your domain and go — TLS is handled for you.

Static or app

A marketing page, your docs, your terms — or the app itself.

1Hosting

Publish in one command

Push your site from the CLI and it's live on a global network in seconds — the cache refreshes itself, no pipeline to babysit.

  • Straight from the CLI One command publishes and refreshes the CDN.

  • Fast everywhere Served from a global network, close to your users.

$ shovelbase sites publish
✓ published → https://yourapp.com
✓ CDN invalidated
2Hosting

Your domain, secured for you

Point your own domain and you're done — the certificate and HTTPS are handled for you, with nothing to renew or check.

  • Bring your domain Point it and go — no config to babysit.

  • HTTPS, handled The certificate is issued and renewed for you.

🔒 yourapp.com

What you'd build with it

The kind of problem Hosting is there to solve.

Use case
The pages the app store requires

Ship your privacy policy, terms, and support page to a real URL so your app clears review.

Use case
Share a prototype this afternoon

Publish what you just built to a real URL and send your team the link — no zip file, no “run it locally” instructions.

Use case
Help and docs on your own domain

Host your FAQ and support pages next to everything else, HTTPS handled for you.

No separate host to configure. The platform serving your backend serves your site too.

Compare shovelbase →

The rest of the stack