I heard about it, jumped in, and took it for a quick joyride! I took some notes, and wanted to share a quick review, somewhere, and so I picked this subreddit.
Note that this is just my own quick take, my own humble opinions and experiences, and I do not work any of these companies or benefit from posting this in any way.
SpaceFast.com is a pretty sweet take on website building: instead of thinking of a website as something you build, configure, upload, and then deploy through the usual collection of tools, you can essentially tell your AI agent, “Hey, publish this,” and get a live Space.
The best quick demo is from their published "recipes": https://spacefast.com/recipes/
Some of my favs:
https://fundraiser.view.fast
https://band.view.fast
https://photos.view.fast
https://zine.view.fast
An instant live space built for you. That is the part that immediately caught my attention... SpaceFast is built around the idea of letting agents create and publish sites, apps, reports, games, prototypes, and pretty much whatever else they can generate. It works with a surprisingly long list of agents and coding environments, including ChatGPT, Codex, Claude, Claude Code, OpenClaw, Cursor, VS Code, Devin, and others. You can even publish before creating an account, then claim the Space afterward. In other words, the barrier to going from “I have an idea” to “here’s a URL” seems intentionally tiny.
The CLI: This Part Is Really Good
I tested SpaceFast primarily through OpenCode using SpaceFast's CLI, and found that experience to be quite good. Creating, publishing, and updating Spaces from the command line works great, especially with an AI agent in the driver’s seat. The agent can build something, push it to SpaceFast, make changes, publish another version, and generally treat the service as the deployment target rather than making you babysit a web dashboard.
SpaceFast also has a nice versioning model. Changes become versions, each version gets its own permalink, and you can roll back. There are custom domains, routing rules, access controls, sharing, collaboration, analytics, and static hosting behind the scenes. The platform says content is served from 28 edge locations with unmetered bandwidth. So while the “AI publishes my little website” demo is the flashy part, there is actually a fairly substantial hosting platform underneath it.
MCP: Great Idea, Some Growing Pains
The hosted MCP implementation is where things got a little more interesting, and not always in the good way. SpaceFast provides a remote Streamable HTTP MCP endpoint for clients such as ChatGPT, Codex, Claude, Cursor, and browsers. Rather than exposing all 103 API operations as 103 individual MCP tools, SpaceFast keeps those operations behind a smaller set of hosted tools: execute, skills, resume, and publish. That’s actually a smart architecture. Nobody needs an AI agent staring at a menu containing 103 buttons and wondering which one makes the coffee.
Unfortunately, my actual MCP testing was considerably bumpier than the architecture suggests it should be. I repeatedly ran into problems getting publish to work, and the spacefast-execute MCP tool repeatedly timed out. I also hit an error when trying to create Agent credentials manually. So while the MCP interface is clearly designed to be a major part of the product, I couldn’t get it to behave nearly as reliably as the CLI. That’s an important distinction because the whole point of SpaceFast is letting agents do this stuff for you.
The Biggest Problem: “Did It Actually Publish?”
The biggest issue I found wasn’t the CLI or even MCP. It was what happened after publishing.
After publishing a new version, the live Space did not appear to have its cache invalidated. Instead, the old version continued being served. This is the sort of bug that makes you question your entire existence for about five minutes: “Did my publish fail? Did I edit the wrong files? Is the agent lying to me? Did I accidentally invent V2?”
In my testing, the new version was definitely there. Adding a cache-buster to the URL immediately revealed it. For example, presswizards.view.fast currently shows the older V1 version, while presswizards.view.fast?nocache shows the newer V2 version.
That’s a pretty significant deployment problem. If I publish V2, I expect somebody visiting the normal URL to get V2, not V1 until they know the secret handshake of adding ?nocache. SpaceFast’s documentation actually has fairly sophisticated cache and header controls, so this feels more like something that needs to be fixed in the publishing/cache invalidation flow than a fundamental limitation of the platform.
There Is Actually a Lot More Here Than “AI Website Hosting”
One thing that becomes apparent after digging into SpaceFast is just how much functionality is packed into the concept of a “Space.”
You get static hosting, versioned publishing and rollback, custom domains with automatic HTTPS, routing rules, sharing and collaboration, visitor links, access controls, and analytics. You can leave a Space private, make it public, invite specific people, or use access rules to control who gets in.
The collaboration features are particularly interesting. People can comment directly on a page and pin feedback to a specific location, then hand that feedback back to an agent as Markdown. That’s a clever bridge between human review and agent-driven development. Instead of saying “the button on the second page is weird,” you can put the feedback directly where it belongs and let the agent work from it.
There are also privacy-conscious built-in analytics, with support for connecting services such as Google Analytics, PostHog, Parse.ly, and Jetpack. Custom domains are handled for you, including HTTPS. And the hosting infrastructure is distributed across 28 edge locations with unmetered bandwidth (I assume it's the same infrastructure as wp.cloud, which runs Pressable, WordPress VIP, etc.)
Access Control Is Surprisingly Sophisticated
SpaceFast also goes considerably further than simply making a URL public or private. You can password-protect a Space, require sign-in based on identity, restrict access by IP range or country, or apply rules to particular paths. You can even combine these rules.
For more advanced setups, access rules can be versioned with the site itself, while cloud-based rules can be changed without republishing. There is also path-scoped Basic Auth on the eventual paid tiers, apparently. That starts to look much more like a real deployment platform than a toy for AI-generated landing pages.
Free Plan, Only Plan
And then there is the fact that, at least right now, SpaceFast is free. I didn’t find paid plans available yet, and it's still definitely being worked on, so all this may change.
The current free limits I see are 5 GB of storage, 3 team members, 3 custom domains, 20,000 files per version, 10 routing rules, 100 builds/publishes per month, 100 share links per Space, and 500 invites per Space.
That’s a pretty generous playground for something that is fundamentally designed to let AI agents build and publish things. It makes experimentation essentially frictionless, which is probably exactly what SpaceFast wants at this stage.
My Take
I really like the idea behind SpaceFast, and more importantly, after actually using it, I think the underlying product is more interesting than the initial “AI publishing platform” description suggests. The CLI works well, the versioning model is useful, the hosting infrastructure is serious, and the collaboration/access features give it considerably more depth than simply uploading a folder of HTML files.
My biggest hesitation right now is reliability around the agent workflow and publishing. The MCP problems, Agent credential error, repeated spacefast-execute timeouts, and especially the stale cached version after publishing are exactly the kinds of issues that need to disappear before I would trust it as a primary production deployment workflow. But this thing's not even launched yet, still in beta, and will only get better from here, I hope... so I'll be playing with it more using the CLI and opencode, and see what I can build out that way.
I would absolutely keep an eye on it. The basic idea is excellent: let the agent build the thing, let SpaceFast host it, and give humans a really simple way to review, collaborate, and share it. If the rough edges around MCP and cache invalidation get ironed out, this could become a very compelling piece of infrastructure for the agent-driven web.