A visual builder can be serious development software. Webflow proved that by giving designers a canvas connected to structure, responsive behavior, reusable systems, interactions, content, and production websites.
Astro offers a different kind of strength. It gives teams a focused framework for building fast, content-driven websites with direct control over the files, components, and services behind them. What it has not traditionally offered is the visual environment many designers use to think.
I come to this as a graphic designer who started building websites in Wix, then learned much more about the web through Webflow. AI-assisted development later made frameworks such as Astro far more accessible. That background is useful here because it makes the gap easy to recognize. The code can be capable, the output can be excellent, and the workflow can still be missing a real design surface.
A new application called sitereal is attempting to fill that gap. It is early, and it deserves the caution any new production tool deserves. But the larger idea is already worth paying attention to: designers may no longer have to choose between a serious visual canvas and an open Astro project.
Astro already provides a strong engine
Astro is a web framework for content-driven websites. It is not a programming language, CMS, CRM, or website builder.
An Astro project organizes pages, layouts, components, styles, content, and interactive features. Its .astro files combine an HTML-like template with CSS and JavaScript or TypeScript, then Astro turns that project into the pages visitors receive.
One of Astro's defining ideas is to send as little JavaScript to the browser as the page actually needs. Most of a page can arrive as straightforward HTML and CSS. A menu, calculator, carousel, map, or other interactive element can be added through Astro's islands architecture without turning the entire page into a large browser application.
That approach can support fast loading and a strong technical foundation for search. It does not guarantee rankings, good design, accessibility, or conversions. Those outcomes still depend on the content and the decisions made around it. What Astro provides is control over the result and a way to avoid shipping unnecessary complexity by default.
For the broader framework decision, our plain-language guide to Astro explains how that foundation differs from a drag-and-drop builder and where it fits in client work.
For developers, that is a compelling foundation. For designers, the foundation has often been visible only through source files, a browser preview, and a development workflow.
What was missing was the editing room
Designing in a browser preview is possible. It is not the same as designing on a canvas.
A typical code-first loop moves between a component, a local browser, a screenshot, and another round of changes. AI can make that loop much faster, but speed does not turn it into direct visual composition.
A serious visual builder puts the page, its structure, and its responsive behavior in the same working environment. A designer can see the hierarchy, select an element, understand where it sits, adjust the relationship, and judge the result in context.
That is not a shortcut around technical understanding. It is another way of reasoning about the website.
Spacing is relational. Type hierarchy depends on what surrounds it. Responsive design is not a desktop page followed by two smaller corrections. Components need to feel consistent across every place they appear. A visual environment makes those relationships easier to see at once.
The value is not that designers can avoid the web. The value is that they can work with the web through the medium they understand best.
Building a good visual tool is difficult
It is easy to underestimate what sits behind a professional visual builder.
The application must represent the page as both a visual composition and a structured document. It needs a layer tree that remains understandable, controls that map cleanly to web properties, breakpoints that reveal responsive behavior, and components that preserve repeated decisions. It needs to manage assets, content, forms, navigation, effects, and motion without turning the interface into a wall of controls.
It also needs to protect the system from its own convenience.
If every adjustment becomes an isolated value, the website drifts. Buttons multiply. Spacing becomes arbitrary. Typography loses its hierarchy. Pages that looked related at the beginning slowly become separate designs.
Professional visual building depends on constraints, reusable components, shared tokens, and clear ownership. The tool has to make the fast action available while still encouraging the coherent system.
That is why the arrival of an Astro-native visual builder is more significant than adding drag-and-drop controls to a code editor. The difficult part is not moving a box. It is preserving the relationship between design intent, website structure, and maintainable output.
sitereal treats the canvas as part of the system
sitereal's visual builder provides a canvas, layer tree, responsive views, style controls, components, templates, content tools, and design-system controls for Astro projects.
Those features will feel familiar to designers who have worked in Webflow or other professional page-building environments. Familiarity is useful here. It means the tool begins with interaction patterns designers already understand instead of asking them to adopt a developer interface with a preview bolted onto it.
The more important point is how those controls relate to the project. Components and templates can carry repeated decisions across the website. Colors, typography, spacing, and other choices can remain connected instead of being recreated page by page. Desktop, tablet, and mobile views can be considered as parts of one design system.
A professional website is not a collection of individually decorated pages. It is a system of repeated decisions.
Navigation should behave consistently. Buttons should not slowly become five different buttons. A section used across several pages should remain one component. Responsive decisions should be visible during design, not discovered after the desktop version is considered finished.
The promise of a tool like sitereal is not simply faster assembly. It is a place where designers can shape those systems directly while Astro remains underneath them.
The output remains a real Astro project
According to its current documentation, sitereal writes ordinary .astro pages, components, styles, content, and supporting files into the project repository. The deployed website does not require a sitereal runtime, and the project can continue to build without an active application license.
That changes the relationship between the builder and the website.
Many visual platforms are also the hosting environment, content system, and permanent operating layer. That integration can be valuable, but it means the project lives inside the platform's boundaries. An Astro-native builder can instead act as an authoring environment for files the team can inspect, version, connect to outside services, and deploy through its chosen infrastructure.
There is still an ownership boundary to respect. sitereal keeps its visual project model in site.sitereal, and files generated by the application can be rewritten when the project is saved. Custom code should live in user-owned files when possible. Existing hand-written Astro pages can remain beside sitereal-owned pages, but the application does not claim to convert every existing page into a fully visual document.
That distinction is healthy. Visual builders do not remove the need for architecture. They make it even more important to know which system owns each part of the project.
Agent access is more useful than another AI box
One of sitereal's most thoughtful choices is that it is AI-friendly without trying to become the user's AI provider.
Many new applications put a prompt box at the center of the product, bundle a limited number of generations, and introduce another credit system or subscription. That approach can make the AI feature more visible than the underlying tool.
sitereal exposes builder operations through an MCP server instead.
MCP, or Model Context Protocol, gives a compatible coding agent a structured way to use an application's tools. Rather than guessing which generated file to edit, an agent can work through operations the visual builder understands. sitereal's agent documentation demonstrates the connection with Claude Code and says other MCP clients can use the server.
This creates a more interesting division of labor. An agent can help create, revise, or organize the site. The designer can inspect the result on the canvas, refine it, test it across breakpoints, and decide whether the work is actually good.
The AI does not have to replace the design tool. The design tool can become accessible to the AI.
That is a better direction for professional work. It lets people bring the agent relationship they already use instead of paying for an isolated assistant inside every application. It also keeps the visual environment focused on the thing it needs to do exceptionally well: represent and edit the website.
This is a good time for small, capable teams
As of October 3, 2026, sitereal is a very new product. Its public changelog lists version 0.2.3, released October 2, after several updates covering content, forms, data sources, GitHub setup, and cross-platform fixes.
The legal notice identifies the publisher as Aufwind Rosebrock & Runnebaum GbR, a two-partner company in Germany represented by Julian Rosebrock and Johannes Runnebaum. That context makes the scope of the application more impressive, not less.
We are living through a period when a small team with the right experience can build a serious professional tool and share it with designers and developers around the world. The work is still difficult. The people making it still need judgment, technical depth, product instincts, and a real understanding of the audience. AI has not made those qualities irrelevant. It has given capable people more leverage.
That may be the most exciting part of this story.
The web does not need every designer to become a framework specialist. It does not need every developer to become a visual designer. It benefits when thoughtful tools let those disciplines meet without flattening either one.
sitereal appears to have been built by people who understand that a professional canvas is not decoration around the code. It is part of how designers create, evaluate, and maintain a system.
Promising does not mean proven
This is an early field note, not a settled recommendation.
The current pricing page lists a seven-day trial, a EUR 69 yearly license, and a EUR 99 lifetime launch price, regularly EUR 199. The license includes commercial and client work, up to three machines for one person, and updates according to the selected term. The official page does not currently list a monthly plan.
I purchased the lifetime license to support the team and have been learning the application for only a few days. The interface feels unusually natural coming from Webflow, and visible improvements have already appeared during that short window.
Before sitereal becomes central to client delivery, it still needs careful testing around updates, generated-file boundaries, repository behavior, agent permissions, platform security, and the full path from a local project to production.
That caution does not weaken the idea. It separates what is promising from what has been proven.
Astro has already shown why a focused, content-first framework can be valuable. Webflow has already shown why visual designers deserve serious tools. Coding agents have shown that more people can work directly with modern technical systems.
An Astro visual builder brings those developments into the same room.
If this category continues to mature, designers will gain more than another way to assemble a page. They will gain a visual way to work with open files, modern frameworks, reusable systems, and agent-assisted development without surrendering the craft that made them designers in the first place.
That possibility is bigger than one application. sitereal is simply the first version of it that has made the future feel close.
If you want help deciding how a visual workflow, content system, and framework should fit together, explore our web design and development work.
Get a quote when you are ready to talk through the fit.