Realtime Infrastructure The pipeline - Capture a live site and get an Astro project back

Start cloning
Talk to us

Capture run

Seventeen phases, one command

Local
6
assets
Alicia
Jonathan
Agent
Agent
Agent
Agent

Fidelity is measured, not claimed.

Every run ends with a headless load of each route, a count of every failed request, and a readiness score. A clone that still has dead references does not pass.

Start cloning
Talk to us

Two engines, chosen automatically.

  • Static engine

    Raw HTTP. Fastest, and higher structural fidelity on SSR sites.

  • Browser engine

    Playwright. For SPA shells and anti-bot CDNs.

Editable output

Components and named slots, backed by your database. No frozen HTML.

Parallel downloads

Concurrent fetches with content dedupe and WebP optimisation.

One CLI, five stages

Run the whole pipeline, or any single stage, against any origin.

  • Capture

    xray capture <url>

  • Refine

    xray refine <in> <out>

  • Wire

    xray wire --site <slug>

  • Verify

    xray verify --strict

  • Deploy

    xray deploy --prod

Asset resolution

Every url(), sprite, webfont and image ref is rewritten to a local path.

Interaction capture

Menus and modals are recorded as DOM diffs and replayed in the clone.

Resumable

A failed stage names the exact command to resume from.

Idempotent re-runs

A capture already on disk is reused unless you ask for a fresh one.

Built to survive real sites.

Behind every clone is a regression-tested pipeline — every asset-loss bug found in the wild becomes a test before the fix ships.

Start cloning
Talk to us

Parallel capture

Concurrent downloads with dedupe. A 250-asset site captures in minutes.

Minimal configuration

One URL and a slug. Everything else has a sane default.

No runtime lock-in

The output is a plain Astro project. XRA is not in the request path.

Isolated tenants

Row-level security scopes every query to its own site.

0 dead references
Astro 5 Output format
Supabase Data layer

Watch every phase as it runs.

The dashboard streams each stage of a capture — assets resolved, routes rebuilt, dead references found — so a bad clone is obvious before it ships, not after.

Start cloning
Talk to us
xracode.com/dashboard
A
Your workspace Studio Site Staging
Overview

Assets captured 253

Routes rebuilt 8

Content slots 1,772

Dead references 0

Capture size 58 MB

More than a capture.

Rebuild a site, own the code, and hand it to a client in one command. Ship a rebuilt site in hours, not sprints .

Point XRA at a URL and get the codebase back

Start cloning
Talk to us