Zero-loss asset capture
XRA captures a live website and rebuilds it as an editable Astro project — real components, content slots, an admin panel and a deploy target. Not a screenshot, not a frozen HTML dump.
A naive scraper saves the HTML and loses everything the browser resolved. XRA runs seventeen phases over the page so what ships is what shipped .
Real Astro components with named content slots — not one minified file you are afraid to touch.
Raw HTTP for static and SSR sites. Playwright for SPA shells and anti-bot CDNs. Chosen automatically.
Every url(), sprite, webfont and image ref is resolved, downloaded and rewritten. Dead references are counted, not ignored.
Copy, media and theme are editable from a CMS wired to your own database. Hand it to a client.
Product and Article JSON-LD are kept verbatim. Sitemap, robots and canonicals are regenerated for the new origin.
Menus, dropdowns and modals are recorded at capture and replayed in the clone — they keep working after the JS is stripped.
XRA turns a reference site into a working codebase in an afternoon — so the work left is design and content , not rebuilding the layout .
A full marketing site captured, rebuilt and deployed the same afternoon.
Plain Astro in your repo. XRA is not in the request path and nothing phones home.
The admin panel lets non-developers edit copy, media and theme without touching the repo.
Tenants share one Postgres and stay isolated by row-level security.
Every page comes back as readable Astro components with named content slots and a typed site config .
Every clone ends with a validation pass that loads each route headless, counts every failed request, and scores the build before you are allowed to call it done.
This page is itself a clone. It was captured from a live product site, rebuilt as Astro components, reskinned, and deployed — in a single session.
Built with XRA Capture to production in one afternoon
Concurrent downloads with content dedupe and WebP optimisation. A 250-asset site captures in minutes.
xray <url> --site <slug> runs capture, refine, wire and deploy end to end.
The output is a plain Astro project. Delete XRA tomorrow and the site keeps serving.
Row-level security scopes every query to its own site, audited after each migration.
Every plan produces the same output: a plain Astro project you own. The tiers only change how many you can run and where they deploy.
One clone a month. Enough to see the output before you pay for it.
For one developer rebuilding sites for a handful of clients.
25 sites a month — four dollars a clone. The tier most studios land on.
Volume rebuilds, on your own infrastructure if you want it.
A clone is one origin captured and rebuilt. Re-running the pipeline on a site you already cloned does not count again.
@ XRA Did the Suisse webfont family survive the refine pass? cc @ Alicia
11 woff2 copied, 0 dead references across 4 routes.
Ship it.