What launched
Automattic, the company behind WordPress.com, launched Spacefast publicly on 9 November 2026 after a soft launch in September. Batuhan İçöz leads the product. TechCrunch reports that İçöz started building Spacefast during an internal Automattic hackathon earlier in 2026, under the working name Stattic. The service hosts the websites, dashboards and small tools that people build with AI assistants, and it supplies backend pieces such as databases, file uploads, email and analytics.
Spacefast's homepage says the service "is not an AI builder". Lovable and similar products put their own chat interface in front of the hosting. Spacefast leaves the building to whatever agent you already use, whether that's Claude Code, Cursor, ChatGPT or a Git push, and handles where the output lives afterwards. For people building agent workflows, the interesting part is how much of the deployment surface Spacefast exposes directly to the agent.
How agents connect
Spacefast's agent documentation describes three ways to wire an agent in. A vendor plugin installs through the client's own marketplace. A universal npx installer covers seven clients. A third option, sf setup agent, reuses your Spacefast CLI login and points the client at a local sf mcp proxy. For Claude Code the docs give these two commands:
claude plugin marketplace add spacefast/plugins
claude plugin install spacefast@spacefastUnderneath, the plugin talks to a hosted Model Context Protocol (MCP) server. MCP is the open standard that lets an AI client discover and call external tools. The Glama directory listing for Spacefast MCP gives the endpoint as https://mcp.spacefast.com, using the Streamable HTTP transport with OAuth sign-in in a browser, so the setup needs no API key. The listing names the server io.github.spacefast/mcp in the official MCP Registry.
The tool design is worth a look for anyone writing their own MCP server. Spacefast doesn't publish one tool per API endpoint. The server exposes a search tool that finds API operations and reads their input and output types without running them, plus an execute tool that runs JavaScript against those operations. This pattern is often called "code mode". The agent writes a short script against a typed API, so a single call can edit source, deploy, change sharing and restore a version. The tool list the model sees stays short, which keeps context use down. The same listing also shows narrower tools for publishing inline files, checking operation status, previewing a Space and resuming a paused task.
Publishing without MCP
Agents that only have a shell can use the plain HTTP API. Spacefast ships a publishing skill file on npm that teaches an agent the flow. An anonymous publish of a single page takes one request:
curl -q -sS -F "[email protected]" https://api.spacefast.com/v1/publishThe response includes a claim URL and an expiry time. A person opens the claim URL to take ownership of the anonymous Space. Owned publishes send a bearer token and upload a zip archive, which queues one CI build. Plain file archives are published as they are. Projects with a build script are installed and built, and the build's output directory is what gets served. A server-bundle app such as a Next.js project without static export gets refused over the API with a build_output_contains_server_bundle error, and the skill file sends the agent to the sf publish CLI command for those projects. A Git remote at git.spacefast.com gives push-to-deploy for teams that would rather keep the agent out of deployment.
The skill file reads like a runbook written for a model, and builders writing skills for their own platforms can borrow from it. The file tells the agent to follow a data.next field (upload, finalize, poll) until the field reports done. The agent should check data.activation.outcome before it reports a site as live, because version status alone doesn't confirm activation. Before creating a new Space, the agent should look for an existing .spacefast/space.json and reuse the Space it finds. Errors arrive as RFC 9457 problem documents, so the agent branches on a stable code field and doesn't have to parse prose. The skill file also tells the agent to keep dotenv files and anything matched by .gitignore out of uploads, and to treat space keys, upload tokens and API keys as secrets that it never prints, logs or commits.
Access controls
New Spaces are private by default. The skill file points out that the bare live URL identifies a site without making the site public. Public access needs an explicit grant through the CLI. Owned Spaces also get an Access URL with an expiry date for sharing previews. According to the agent docs, agents act within permissions the user approves, and team membership and billing changes can only be made by a person in the dashboard. A paused, approval-gated task resumes through resume_execution. German outlet Dr. Web reports that rollbacks and DNS changes need approval as well. We couldn't find that detail in Spacefast's English docs, so we'd test it before relying on it.
Costs and limits
The pricing page lists four plans, billed monthly in US dollars before tax:
- Personal: US$0, no card, US$1 of included usage, 20 Spaces, 1 GB disk per Space, daily backups kept 7 days, commercial use allowed
- Go: US$5 a month, 100 Spaces, 10 GB disk per Space, hourly backups, datacentre choice
- Pro: US$15 a month, 500 Spaces, 25 GB disk per Space, up to five members included and US$15 a month for each extra member
- Enterprise: custom pricing, SSO, SAML and SCIM, egress firewall and log drains
Usage beyond the included amount bills at the end of the month. Go and Pro accounts can set a spending cap that starts at twice the plan price, with alerts at 50, 75 and 100 per cent. A US$9 Boost add-on raises one Space to 8 compute workers. Because an agent can create Spaces and trigger builds without a person watching, we'd set the cap before connecting one.
Several things remain unknown. The pricing page offers a choice of datacentre on Go and above but doesn't name the locations, so we can't say whether any of them sits near New Zealand. Auckland users could see latency on database-backed apps, and anyone storing personal information should know where that data lives. The skill file tells agents to publish first and read the diagnostics without guessing limits, which suggests the per-request limits aren't fully documented yet. TechCrunch also notes that Automattic has recently gone through a board dispute, executive departures and layoffs. We'd weigh that history before moving anything long-lived onto a new product.
What builders could do with it
The best fit is short-lived, low-risk output: internal mockups, demo pages for a client meeting, a dashboard that an analysis agent regenerates each week, or a prototype you want colleagues to click through. TechCrunch reports that early users mostly publish mockups, slideshows and sales pages. Pairing private-by-default Spaces with expiring Access URLs works well for showing work to a few people without opening it to the whole internet.
People building agents can learn from Spacefast without becoming customers. Code mode, machine-readable error codes, explicit "is the site actually live" checks and human-only billing actions are patterns any MCP server author can copy. If you build something on Spacefast, or your own server borrows these ideas, you can share it on the ASAI projects page.
Sources
- Spacefast agent documentation
- Spacefast publishing skill (SKILL.md, npm package spacefast 0.4.1)
- Spacefast pricing
- Spacefast homepage
- TechCrunch: Automattic debuts a platform to deploy vibe-coded apps
- Glama: Spacefast MCP server listing
- Dr. Web: Spacefast, Automattic hosting for AI agents
Build with people working on the same things
Join the Auckland Society for AI: NZ$599 a year with a ForgeBox and the members' projects area. Our Auckland meetups are open to everyone.