Automattic opened Spacefast publicly on November 9, 2026, following a September soft launch. The platform connects AI agents to hosting, domains, and a SQL database; built-in application-user authentication is still forthcoming.

From generated code to a working address

It offers API, CLI, and MCP interfaces, versions, and approval checks for sensitive operations. Documentation separates declaration, upload, finalization, and activation. Ready does not mean live. Preview can finalize a version without activation. A long operation may require checking progress rather than uploading again.

A free plan still has boundaries

At verification, the documentation offers Personal without a base monthly subscription, alongside limits and charges for individual resources. Concurrent dynamic requests, for example, are limited. Some storage and compute categories are temporarily complimentary. This is a description of current terms, not a promise of an unlimited free application or a fixed future price.

These details matter because generating a website does not finish the job of operating it. Data handling, error observation, and access management remain after code generation. That is our editorial interpretation of the boundary between creation and operation, rather than another provider guarantee.

Four checks before practical use

For an illustrative internal catalogue, we would begin with test records and limited access. The first check is whether the page works at its final address. The second is whether a submitted record actually persists and can be read after reopening the application. A visible form alone establishes neither of those outcomes.

The third check is which version serves users. A successful build's address can be useful for review while the active application still shows an earlier version. An agent should report actual activation, rather than merely a completed upload. When an outcome is uncertain, checking the operation status is more useful than immediately publishing again.

The fourth concerns recovery. Restoring files to a previous version does not automatically establish that every data change has also been reversed. If a new form stored different fields, the team must check how the older application interprets them. This is a general architectural question, not a defect that SIExpo has discovered in Spacefast.

For a team changing AI tools, separating infrastructure from the conversation may be convenient. However, portability should be evaluated through the actual files, databases, and interfaces the application uses. Supporting a common agent protocol does not make every hosted application interchangeable.

An initial review should also give the owner a clear description of what has become public, who may alter it, and which resources can produce charges. The deployment receipt and the visible application should agree. A convenient conversational interface helps only when its summary remains connected to those concrete outcomes.

Spacefast addresses an often underestimated stage after code generation. SIExpo verified the accessible announcement and documentation but has not deployed its own application on the service. Reliability, cost, and suitable access still require a bounded pilot with explicit acceptance criteria.

Sources: Automattic — public Spacefast announcement, Spacefast — publishing states and receipts, Spacefast — current pricing and resource limits. The cover is a conceptual AI illustration, not a documentary photograph.

Editorial verification: 2026-11-11T07:14:46.966546+00:00.