Give your agent a real website.Not a page builder to fight.
SiteSpring hands Spring, or any agent you trust, a full Astro project it can read, edit, build and deploy. Real source files. Real build errors. Shipped to the edge in seconds, and rolled back faster than that.
Three things, and nothing in between.
01
The workspace is the draft
Every site is a real Astro project on its own Durable Object, with a SQLite filesystem behind it. Your agent reads and writes source files directly. The workspace persists between conversations, so picking a thread back up does not mean checking anything out.
02
Build and look at it
The agent runs the real build, reads the real errors and fixes them. Preview publishes to its own hostname, noindex, so you can open the thing in a browser before anyone else can find it.
03
Deploy, and roll back faster
Deploy uploads the built site as its own Worker at the edge and snapshots the artifact. Rollback replays a previous snapshot without rebuilding, so recovering from a bad change takes seconds and leaves the draft untouched.
The whole surface an agent gets.It is not a long list on purpose.
Every tool is defined once and projected to both the CLI and the MCP server, so the two can never drift apart. There is no separate set of blocks or components to learn. If your agent can write Astro, it can use this.
- read, write, edit
- Direct filesystem calls on the workspace. No backend starts.
- ls, stat, find, grep
- Search and inspect the source. Structured results, not stdout to parse.
- exec
- A fast in-Worker shell for text work, or a full Linux container when the task needs Node.
- build, check, preview
- The real Astro toolchain, wrapped so the agent never shells out to it.
- deploy, rollback, status
- Ship it, undo it, and see what is live versus what is drafted.
Built on Cloudflare, end to end.
Durable Objects
One per site. Owns the draft filesystem and the build container.
Workers for Platforms
Each site is its own Worker, routed by hostname at request time.
R2
Build artifacts, which are the only thing a rollback needs.
D1
The site registry, deploy history and form submissions.
This page is the demo.
It is a SiteSpring site. An agent scaffolded the project, wrote these files into the workspace, ran the build, read the output and deployed it. Nothing here was assembled by hand and uploaded.