Astro solves the technical half of a modern website remarkably well. What it does not give designers is a place to design.
That gap matters because a visual canvas is not merely a shortcut around code. It is where designers judge hierarchy, spacing, responsive relationships, and the repeated decisions that make a website feel like one system.
Webflow proved that serious web work can happen visually. My own path from graphic design into web development made that lesson hard to forget. When AI-assisted development made Astro more accessible, the output was excellent, but the work still felt indirect.
An Astro visual builder offers a more interesting possibility: keep the real project, then give designers another way to work with it. A young application called sitereal is an early example of what that category could become.
What an Astro visual builder actually adds
Astro is a web framework for content-driven websites. It is not a programming language, CMS, CRM, or website builder. It organizes pages, components, styles, content, and services, then turns them into the pages visitors receive.
Astro also tries to keep browser JavaScript focused. Most of a page can arrive as HTML and CSS, while a menu, calculator, carousel, or other interactive feature can load through Astro's islands architecture. That can support fast loading and a strong technical base for search, though it cannot guarantee rankings, accessibility, or conversions.
A visual builder adds the missing work surface: a canvas, layers, responsive views, and reusable components connected to that Astro foundation. Our plain-language guide to Astro covers the framework itself in more detail. The question here is what changes when designers can finally see and shape the system directly.
A canvas is more than drag and drop
In a code-first workflow, a designer often moves between a component, a browser preview, a screenshot, and another round of instructions. AI can accelerate that loop. It does not turn the loop into direct composition.
On a canvas, the relationships are visible at once. A heading can be judged against the image below it. A section can be tested across breakpoints before the desktop version feels finished. A shared button can be corrected once instead of drifting into five slightly different buttons.
The hard part is not moving a box. A professional visual tool must make direct manipulation easy while preserving the constraints that keep the website coherent.
Designers should not have to abandon visual reasoning to gain access to a modern, open project.
The real test is whether the builder preserves the system
sitereal's visual builder combines a canvas and layer tree with responsive views, components, templates, content tools, and design-system controls. The interaction model feels familiar to someone coming from Webflow, but the more important question is what happens beneath the canvas.
Reusable components can carry the same navigation, section, or button across the site. Shared colors, type, and spacing can remain connected instead of becoming isolated page-level choices. The canvas is useful because it exposes those relationships, not because it hides the web.
That is the category's real promise: visual speed without visual drift.
One project, three ways of working
According to its current documentation, sitereal writes ordinary .astro pages, components, styles, content, and supporting files into the repository. The deployed site does not need a sitereal runtime, and the project can continue to build without an active application license.
That does not remove ownership boundaries. sitereal keeps its visual model in site.sitereal, and generated files can be rewritten when the project is saved. Custom code should live in user-owned files when possible, and an existing hand-written Astro page does not automatically become a visual document.
The same principle makes its agent approach interesting. Instead of selling another isolated AI prompt box, sitereal exposes builder operations through an MCP server. MCP, or Model Context Protocol, gives a compatible coding agent structured access to an application's tools. sitereal's current documentation demonstrates Claude Code and says other MCP clients can use the server.
The designer can work through the canvas, the developer can work through the files, and the agent can work through structured operations. They are different access points to one project.
Promising does not mean proven
This is an early field note, not a settled recommendation. As of October 3, 2026, sitereal's public changelog lists version 0.2.3. Its pricing page lists a EUR 69 yearly license and a EUR 99 lifetime launch price, regularly EUR 199. Its legal notice identifies a two-partner company in Germany. A small, experienced team building something this ambitious is part of what makes the moment exciting.
This article is not sponsored. I purchased the lifetime license to support the team and have used the application for only a few days. It already feels natural coming from Webflow. Before I rely on it for client-critical work, I still want to test updates, generated-file boundaries, repository behavior, agent permissions, platform security, and the path from local project to production.
The product is early. The idea is larger. Designers may no longer have to choose between a serious visual canvas and an open modern project.
If you are deciding how a visual workflow, content system, and framework should fit together, explore our web design and development work.
