Ship a static site without writing a Dockerfile

Most front ends do not need a container. They need a bucket, a CDN edge and a certificate. But the standard cloud workflow still asks you to write a Dockerfile, pick a base image, configure nginx and keep all three patched — for a folder of files that never executes anything.

Simplifyd has a static site service type that skips the whole detour. You create the service, publish your built assets, and they are served from object storage behind our edge.

Create the service

From the console, create a service and choose Static site. There is no image to pick and no port to expose, because nothing is running — the bucket is the service.

Publish your files

Files are published inline through the API, so anything that can make an HTTP request can deploy. The CLI wraps it:

npm run build
simplifyd static publish ./dist

That last command replaces the previous contents in place. There is no build step on our side to wait for and no window where half the old site is serving next to half the new one.

Or let an agent do it

Because publishing is a plain API call rather than a Docker build, an AI agent connected over MCP can deploy for you. Point Claude at your repo, connect the Simplifyd MCP server, and "build this and publish it" is a single instruction — no local Docker daemon, no registry login, no CI runner.

This was the actual reason we built inline publishing the way we did. An agent cannot run a Docker build inside a chat session, but it can absolutely send files to an endpoint.

Attach your domain

Custom domains attach as bucket aliases and certificates are issued automatically. Point a CNAME at the address we give you and the certificate follows.

A static site should cost you one command and one DNS record. Everything past that is accidental complexity someone else decided you needed.

If you have been putting off moving a marketing site or a docs build because the container work was not worth it, this is the path that removes the excuse.