Draw the page on a canvas that edits files
Every breakpoint at once, a tree carrying your own class names, and a Style panel writing into the one rule that actually styles the element. Select a heading and .hero__title opens — not a copy of it.
Let an agent build it. Keep the file it wrote.
sitereal ships an MCP server over the same HTTP API the canvas uses, so Claude Code — or any MCP client — creates pages, components, templates and design-system values while you watch the canvas update. What lands on disk is ordinary .astro you can edit by hand five minutes later, or five months later.
Paste HTML, get a tree. Read the tree, get the HTML back.
Same class names, no builder-owned wrapper, and no generated name you did not choose.
Everything your site needs, built into sitereal
Design
Compose responsive pages on a visual canvas.
Code
Read and edit the real HTML and CSS.
Agents
Let Claude Code build and maintain pages.
MCP
Connect any MCP client to the open project.
Reuse
Components, templates, snippets and presets.
Design system
Eighteen modules of tokens you can switch off.
Content
One schema gives you types, forms and queries.
Motion
Reveals and scroll links, as plain attributes.
SEO
Titles, structured data, sitemap and robots.
Ship
Its own git repository. Hosts anywhere.
Three moves, and the third one is git push.
There is no publish button that phones home, because there is nothing to phone — branches, pull and push are plain git against your own remote.
- Step 01
Open a folder
Point sitereal at an Astro project you already have, or scaffold a new one. It gets its own git repository at once — a site’s history has nothing to do with the tool that drew it.
- Step 02
Compose
Sections, containers, elements. Style through the token layer or write the CSS yourself in the same panel: the two are views of one stylesheet, not a round trip.
- Step 03
Commit
Save, and real files land under src/. Push them. Deploy to Netlify, Vercel, Cloudflare, a bucket or your own box. Nothing on that server has ever heard of sitereal.
origin/main · 2 commits behind
meinaufwind/sitereal · 3 to push
Branches
Every branch the repository has, local and on origin, and a field that starts a new one. A switch is refused while the tree is dirty rather than dragging uncommitted work onto another branch.
Pull
Fetch and rebase onto origin, autostashed, so whatever you were in the middle of survives it. On a conflict git stops and you are handed its own message, not a summary of it.
Push
Stage, commit and push to origin, in one press. Nothing is ever committed or pushed on your behalf — the engine runs git when you ask it to and at no other moment.
A folder of finished pages. Nothing to attack, nothing to wait for.
sitereal builds an Astro site, so what you upload is HTML, CSS and images. No PHP on the host, no admin login on the public site, no plugin surface and no database unless you asked for one — and because every page was rendered before anyone asked for it, there is nothing left to compute while a visitor waits.
Nothing on the host to break into
A static site is files being served. There is no wp-admin, no plugin with a CVE in it, no database credentials sitting on the machine. The builder runs on your own computer and is never part of the deployed site, so the attack surface a CMS gives away for free simply is not there — and a form's delivery keys stay in environment variables on your host, never in the page.
Zero JavaScript until you ask for some
Astro renders your components at build time and ships no framework runtime by default. Interactivity is an island, loaded only where you place one, and sitereal's own runtimes — motion, navigation, forms, overlays — are a few kilobytes each and emitted only for the pages that actually use them.
The page is finished before the request arrives
Every route is built once and served as a file, from a CDN, an object store or the cPanel plan a client already pays for. Nothing renders per visit, so there is no cache plugin to invalidate, no page that gets slower under load, and hosting costs what static hosting costs.
Answered plainly.
If something here is still unclear, the documentation goes considerably deeper.
Read the docsWhat does it cost?
Seven days free with every feature, then €69 a year — or €99 once at the launch price, regularly €199. The two licenses give you the same application and differ only in how long they run: the lifetime license never ends, and a yearly license runs for as long as you renew it. When it ends, sitereal stops opening projects until you renew — your sites are ordinary files and keep building without it. Full details are on the pricing page.
What exactly does it write into my project?
src/pages/<route>.astro for each page, src/components/<Name>.astro for each component, the generated stylesheets under src/styles/generated/, the small runtimes under public/scripts/, and your content and media as ordinary files. One extra file, site.sitereal, holds what the canvas knows — and the site never reads it.
Can I hand-edit the code afterwards?
Yes, and that is the point: visual editing and hand-editing are two views of the same files. The generated files are rewritten on save, so keep your own work in your own files — everything else in the repository is yours and safe to edit normally.
Does it work with an existing Astro site?
Yes. Point it at the folder. It adds its own files and leaves yours alone; pages you have written by hand stay yours, and the ones you draw appear alongside them.
Which platforms does it run on?
macOS, Windows and Linux. It is a desktop application, and each project window runs its own local engine. Builds are on the releases page.
Can I use it for client work?
Yes, on either license, with no separate commercial tier. The sites you build are yours and your clients', with no attribution required and nothing of ours left running in them.