Your site, served from
just round the corner.
Every Shipmunk site goes out from a global edge network in hundreds of cities, so visitors get it from somewhere near them. Underneath, releases never change once they're made, and going back is a switch, not a rebuild.
- 100sof edge locations worldwide
- 0servers to boot per visit
- 1switch to roll back
- UK + EUwhere your data is stored
Three jobs, kept apart.
One release flows through them.
Managing your projects, storing your files and serving your sites are separate systems. Each one does one thing, and a problem in one doesn't take the others down.
Your tools send releases to the control plane, build plane and file storage. Releases are published to the global edge, which serves your visitors.
- Accounts, workspaces, projects
- Release records and approvals
- Checks before anything goes live
- Domains and certificates
- Your machine, your browser
- Soon: a fresh short-lived machine
- Every file stored by its hash
- Releases never change
- Hostname → live release
- TLS for every domain
- Cached near your visitors
- Redirects and headers
- Built-in, preview and portal addresses
What happens when someone visits.
Four steps, all at the edge, none of them on a server you have to think about.
- 01A visitor asks for kiln.design
Their request goes to the nearest of our edge locations, usually in their own country.
GET kiln.design/classes - 02The secure connection ends nearby
HTTPS is handled right there, with a certificate we issued and renew for you.
🔒 TLS · valid · auto-renews - 03The edge finds the live release
One lookup: this hostname, this release. Redirects and headers from your _redirects and _headers apply here.
kiln.design → r_8f3c21 - 04The file comes from close by
Usually it's already cached at that location. If not, it's fetched once from storage and kept for the next visitor.
● cache HIT · served nearby
Ship only what changed.
Keep every version.
Every file gets a fingerprint of its contents. When you ship, we ask which fingerprints are new, and you upload only those.
✓ 139 files already stored · 3 uploaded · 0.9s
A release is a fixed list of files. Going live, or going back, just points your domain at a different list. Nothing is rebuilt or re-uploaded.
- r_10ab3f20 Oct
- r_4c773127 Oct
- r_5e9a4429 Oct
- r_8f3c21TodayLIVE
Built for code nobody's fully read.
A lot of sites are written by AI now. We treat every site as untrusted and put walls between your sites, your account and everyone else's.
Stored in the UK and EU.
Delivered everywhere.
Prices in pounds, invoices with UK VAT, and your data kept close to home.
The same fast edge.
Built for client work.
Vercel and Netlify are excellent hosts, and the basics are a match. Where Shipmunk differs is everything around your clients, and how you're billed.
| FEATURE | Vercel | Netlify | |
|---|---|---|---|
| Global edge delivery | Yes | Yes | Yes |
| A preview link for every release | Yes | Yes | Yes |
| Roll back without rebuilding | Yes | Yes | Yes |
| MCP server for AI agents | Yes | Yes | Yes |
| Prices billed in | Pounds (£) | US dollars ($) | US dollars ($) |
| How usage is billed | [Flat monthly plans] | Platform fee plus metered usage beyond included credit | Monthly credits, with top-ups |
| Clients review on your branded portal and domain | Yes | Not built in | Not built in |
| Client sign-off recorded before going live | Yes | Not built in | Not built in |
| Clients comment on previews without signing up | Yes | Needs a Vercel account | Needs a Netlify login |
Based on each company's public pricing and documentation as of [November 2026]. Features and prices change, so check vercel.com/pricing and netlify.com/pricing for the latest. “Not built in” means it isn't a built-in feature of their standard plans. Vercel and Netlify are trademarks of their owners; Shipmunk isn't affiliated with either.
Static sites first.
More when it's ready.
Fast for your visitors.
Boring for you.
The good kind of boring. Ship your first site free.