Hosting for platforms

AI builders turning a prompt into a working app. Tools for landing pages, wedding invitations and digital cards. Portfolio, résumé and restaurant menu builders. Proposal and pitch tools that hand a client a link instead of a PDF. Agencies running client work at volume. And whatever the next one turns out to be.

You have built the part that makes the site. This is the part that puts it online, already running, with your name on it instead of ours.

The second product

Putting a generated site online, for thousands of people who are not engineers, is more than a bucket and a CDN:

Domains and DNS

Subdomains for your users, and the custom domains they bring. Records, verification, propagation.

Certificates

Issued and renewed for every hostname, forever, without anyone having to think about it.

Versions and rollback

Every publish kept as its own snapshot, so a bad release is undone by moving a pointer.

Abuse

Scanning, takedowns, and the day someone hosts a phishing page on your domain.

Edge delivery

Fast everywhere, cached correctly, unbothered when one of your users goes viral.

The long tail

Redirects, rewrites, SPA routing, custom headers, password-protected drafts.

None of it differentiates you, all of it has to work, and your users notice it only when it breaks.

How much your users see is your choice

The platform is modular. Take all of it or one piece of it; the difference is only how much reaches your users.

Invisible

Your product publishes in the background. A site appears at theirname.yourplatform.com, your user sees a link, and nothing in the flow says where it came from.

Partly yours to expose

You surface what is worth surfacing inside your own interface: connecting a domain, browsing earlier versions, restoring one. It reads as a feature of your product, because it is one.

The whole toolkit, rebranded

Your users get everything we give ours, carrying your name. They upload and manage their own sites and domains, and point their own agents at your publishing endpoint.

Under your name

Sites live on your domain. Subdomains you hand out, like theirname.yourplatform.com, or domains your users own, like www.theircompany.com, connected and verified without them ever leaving your product.

What we serve is what you uploaded. The deploy path is a pure pipe, so nothing is injected or rewritten, and no badge or footer of ours appears on a page. One response header, x-deployment, names the snapshot being served. It is the only trace of us anywhere.

The pieces

Eight ways to publish, all in production, all used by our own customers. Hand your users any of them under your name; the ones you leave out never appear.

Web console: upload, manage and roll back

REST API: what all the others are built on

CLI: one command, scriptable

SDK: typed, browser and Node

MCP server: your users' AI agents publish directly

Agent skill: one file that teaches any agent to ship

GitHub Action: publish on push

n8n node: publish from a workflow

Before you build on it

Three things worth knowing now rather than during integration.

Every hostname is registered explicitly

No wildcard mapping. You create each one as a user needs it: a single call, and an exact record of what exists.

Static files only

No server-side execution and no build step. You generate however you like and hand us the output. If your users need rendering at request time, this is the wrong layer.

DNS belongs to whoever owns the domain

Yours to set once, for your own domains. Theirs for the ones they bring, and we return the exact records to show them. Routing is CNAME-based, so a bare domain redirects to its www subdomain.

Pricing

There is no published price. The right shape depends on how you publish and at what volume, so it is the first thing we work out together.

We invoice you; your users never transact with us.

Talk to us

Email hello@shipstatic.com with what you are building, how many sites you expect in the first year, and how much of this you want your users to see. Enough for us to come back with a real number instead of booking a call.

Publishing your own sites rather than other people's? The standard plans are probably what you want.