Sites (beta) · 3 November 2026

Static websites served with no machine

A site is files and a route table (redirects, rewrites, headers, Markdown for agents, 404 pages) served by every front. POST /v2/sites creates one; :missing returns the files, by SHA-256, the site does not hold yet, :upload stores each, :release stages a release and :publish makes it live in one commit. :rollback publishes the previous release, also in one commit, and keeps the release it replaced so it can be published again. Both :publish and :rollback accept ifVersion and return 409 if another change came first. :releases returns the live release, the earlier ones and the ones rolled back from. A deleted site stops serving and keeps its releases; restoring it serves its live release again. npx withruntime sites deploy ./dist runs all of these for a folder and uploads only the files that changed. Every SDK, the CLI and the MCP tools include Sites. Usage is billed on the existing storage, operations and egress meters at their current rates.