THE PLATFORM

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
ARCHITECTURE

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.

YOU SHIP FROM$CLIShipIDE⎇Git push⌘Your AI agent (MCP)
LONDONControl plane
  • Accounts, workspaces, projects
  • Release records and approvals
  • Checks before anything goes live
  • Domains and certificates
ISOLATEDBuild plane
  • Your machine, your browser
  • Soon: a fresh short-lived machine
EUFile storage
  • Every file stored by its hash
  • Releases never change
HUNDREDS OF CITIESGlobal edge
  • Hostname → live release
  • TLS for every domain
  • Cached near your visitors
  • Redirects and headers
  • Built-in, preview and portal addresses
WHO GETS ITVisitors, worldwideYour clients, in their portalSearch engines and bots
moves when you ship moves on every visitYour live sites never touch the control plane
Your live site doesn't depend on our dashboardVisits are answered entirely at the edge. If our dashboard or API has a bad day, your sites keep serving.
Nothing boots when someone visitsStatic files sit ready at the edge. No server to wake, no cold start, no queue.
Files are stored onceEvery file is kept by a fingerprint of its contents. Ship again and only what changed is uploaded.
Builds never share a runnerYour machine or your browser tab. Server builds, when they arrive, get a fresh short-lived machine that's thrown away afterwards.
ANATOMY OF A REQUEST

What happens when someone visits.

Four steps, all at the edge, none of them on a server you have to think about.

  1. 01
    A visitor asks for kiln.design

    Their request goes to the nearest of our edge locations, usually in their own country.

    GET kiln.design/classes
  2. 02
    The secure connection ends nearby

    HTTPS is handled right there, with a certificate we issued and renew for you.

    🔒 TLS · valid · auto-renews
  3. 03
    The 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
  4. 04
    The 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
ANATOMY OF A RELEASE

Ship only what changed.
Keep every version.

Upload by fingerprint142 files · 3 changed

Every file gets a fingerprint of its contents. When you ship, we ask which fingerprints are new, and you upload only those.

$ npx shipmunk deploy
✓ 139 files already stored · 3 uploaded · 0.9s
Releases never changekiln.design

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.

  1. r_10ab3f20 Oct
  2. r_4c773127 Oct
  3. r_5e9a4429 Oct
  4. r_8f3c21TodayLIVE
Roll back moves the LIVE pointer. Previews of every release stay up too.
SECURITY

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.

Your sites live on their own domainPublished sites and previews are served from a different domain from your dashboard, so site code can never reach your account.
Workspaces are walled off twiceEvery request is checked in our API, and again by the database itself, so one workspace can never read another's data.
Builds stay apartBuilds run on your machine or in your browser tab, never on a runner shared with anyone else. Server builds, when they arrive, get a fresh short-lived machine.
Agents get small keysTokens for AI agents are scoped to one project, ship previews only by default, and can be revoked in a click.
Checks before anything goes liveExposed API keys are caught before a release is promoted. If a check fails, your live site stays as it was.
Certificates handled for youEvery domain gets HTTPS, issued and renewed automatically. We check your DNS before we call a domain live.
DATA

Stored in the UK and EU.
Delivered everywhere.

Prices in pounds, invoices with UK VAT, and your data kept close to home.

LONDONAccounts, projects and approvalsYour workspace, your clients and every sign-off are stored in a London region.
EUYour site's filesEvery release is stored in EU-only storage.
WORLDWIDEYour published sitePublic pages are cached at edge locations near your visitors, wherever they are. That's what makes them fast.
HOW WE COMPARE

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.

FEATUREShipmunkVercelNetlify
Global edge deliveryYesYesYes
A preview link for every releaseYesYesYes
Roll back without rebuildingYesYesYes
MCP server for AI agentsYesYesYes
Prices billed inPounds (£)US dollars ($)US dollars ($)
How usage is billed[Flat monthly plans]Platform fee plus metered usage beyond included creditMonthly credits, with top-ups
Clients review on your branded portal and domainYesNot built inNot built in
Client sign-off recorded before going liveYesNot built inNot built in
Clients comment on previews without signing upYesNeeds a Vercel accountNeeds 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.

TODAYStatic sites and front endsBuilt on your machine or in ShipIDE. Backends pair with Supabase, Firebase or any API.
COMINGBuilds on every Git pushIn isolated, short-lived machines, using the same release flow.

Fast for your visitors.
Boring for you.

The good kind of boring. Ship your first site free.

Start shipping$npx shipmunk