Spacefast

Publish the sites your agents build. One command, a live URL, immutable versions, custom domains.

Spacefast hosts the sites people build with AI agents. You hand it a folder, it hands back a URL. Publish from the dashboard, the sf CLI, the HTTP API, or an MCP server. An agent with publishing permission can ship the site it built.

Prefer a browser to a terminal? Drag a folder onto the dashboard instead — no install, no account required. See Drop.

Publish in one command

npm install -g spacefast

sf publish ./dist

No account needed for the first publish. The CLI creates a Space, uploads the files, and prints a live URL plus a claim link. Sign in later to keep it.

Published: https://quiet-harbor.space.fast

  Open          https://quiet-harbor.space.fast
  Version URL   https://quiet-harbor--v1.space.fast
  Version       v1 (ready)
  Files         12
  Duration      3.2s

Or ask the agent that built it.

How it fits together

A Space holds a site and its versions, immutable snapshots with their own URLs. A publish with no changes can reuse the current version. The live channel points at the version visitors see, or is empty before the first publish. Promoting or rolling back to a retained, ready version moves that pointer without rebuilding. Preview publishes and manual promotion policies leave live alone. (New terms piling up? See the glossary.)

Static output is the default path. Point sf publish at a build directory and it uploads only the files that changed. If you’d rather publish source, Spacefast detects the framework and builds it. Sites that need a database, server functions, or scheduled jobs declare a Zero runtime and server entry.

In a self-serve account, your team owns the Spaces you claim, even when you are its only member. On Plus, you can add members who publish and roll back without sharing your login. Free and Go allow only the owner. Team roles control who can manage domains, credentials, and billing. See Teams and members to invite people and choose how new Spaces are shared.