← All articles

astro preview before deployment

How to Preview Your Astro Site Before Deployment

Your Astro build compiled without errors. Now get feedback from a teammate or client without pushing to Vercel or waiting for a preview deploy.

Published June 3, 2026 Updated June 4, 2026 5 min read
In this article

Astro’s built-in astro preview command lets you preview your production build locally. It catches build-time issues before they hit production. It renders your site exactly as it will ship. But the moment you need someone else to see it, you’re back to deploying, and that’s the part that slows teams down.

You’ve built your Astro site. astro build compiled without errors. Now you want a teammate, a client, or a stakeholder to review it before it goes live. You could push to Vercel or Netlify and wait for a preview deploy. Or you could share a temporary public URL straight from your local machine, skip the deployment altogether, and get feedback now.

That second option is where WireMaven fits. This tutorial walks you through the workflow: from astro dev to a shareable preview URL, with visibility into who viewed your build and whether they hit any errors.

The Astro Dev Workflow: Dev, Build, Preview

Astro gives you three core commands for local development:

CommandWhat It Does
astro devStarts a hot-reloading dev server at localhost:4321. Great for fast iteration.
astro buildCompiles your site to static output in the dist/ directory.
astro previewServes the production build locally so you can check it before deploying.

The typical flow looks like this:

# Start development
astro dev

# Build for production
astro build

# Preview the production build locally
astro preview

astro preview is useful, but it has a limitation: it binds to localhost. Only you can see it. If you need a teammate to check a page, or a client to review a layout, localhost does not help.

This is where developers usually turn to preview deploys. Vercel and Netlify offer them as part of their Git-based deployment pipeline. Every PR gets a unique URL. That works, but it takes time. Your code needs to commit, push, build, and deploy before anyone can look at it. For quick reviews during active development, that cycle is heavy.

Sharing an Astro Build for Review Without Deploying

WireMaven gives your local dev server a temporary encrypted public URL. No commit, no push, no build pipeline. You run one command, share a link, and your reviewer sees your site live from your machine.

The difference matters in three specific scenarios:

  1. You’re mid-feature and want a quick design check. Committing half-done code to trigger a preview deploy creates noise in your Git history and clutters your deployment pipeline.

  2. Your build takes 3+ minutes and preview deploys add another 2 minutes on top. That is 5 minutes of waiting every time someone asks “can I see that real quick?”

  3. You want to know if the reviewer actually opened the link and whether they hit any broken pages. Preview deploys tell you the deploy succeeded. They do not tell you whether anyone looked at it.

WireMaven solves all three with a session-aware tunnel that shows you viewer activity, request outcomes, and error counts in real time.

Step-by-Step: Preview Your Astro Site with WireMaven

Option A: Framework integration (package path)

Install WireMaven as a dev dependency, init it once, and the tunnel starts automatically with your dev server.

npm install -D wiremaven
npx wiremaven init
npm run dev

wiremaven init detects Astro and patches your config. After that, every npm run dev starts both your Astro dev server and the tunnel. The public URL appears in the in-browser overlay — no separate command needed.

Option B: Standalone CLI (no project changes)

If you prefer not to modify your project, use the standalone CLI:

npx wiremaven-cli 4321 --expires 30m

The CLI outputs the public URL directly:

Wiremaven tunnel ready: https://relay.wiremaven.com/p/abc123/
Local control API: http://127.0.0.1:2999

The public URL uses the relay’s domain (relay.wiremaven.com) with a path-based token — not a subdomain. Share that URL with your reviewer.

When to Use a Tunnel vs Deploy Previews

Tunnels and deploy previews solve different problems. Knowing which to use saves time for your whole team.

Use a tunnel when:

  • You are actively iterating and need a second pair of eyes
  • The change is small enough that a full deploy cycle feels wasteful
  • You want real-time feedback on whether the reviewer saw the change
  • You are debugging an issue that only surfaces in certain environments and need someone else to reproduce it
  • You are doing an async design review where you want to know which pages the reviewer visited

Use a deploy preview when:

  • The review is part of a formal PR approval process
  • Multiple team members need to review the same build independently over time
  • The build is final and doesn’t depend on your local machine staying online
  • You need a permanent record of the review (Git-based deploy previews persist with the PR)

A practical workflow is to use WireMaven during active development for fast iteration, then fall back to a deploy preview once the branch is ready for final review. Tools like deploy-to-demo workflows have hidden costs that compound when every small check-in triggers a full build pipeline.

WireMaven gives you more options in the middle of that cycle. Instead of deploy-or-wait, you can share a temporary public URL from your local dev server in seconds and get feedback immediately.

Session Control: Duration and Expiry

WireMaven tunnels auto-expire. When using the standalone CLI, choose 15, 30, or 60 minute sessions:

npx wiremaven-cli 4321 --expires 60m

When the session expires, the URL stops working. Your local server stays exactly as it was. No cleanup, no dangling links, no stale preview URLs floating around in Slack threads.

This is useful for scheduled reviews. You set a 60-minute window, share the link with a client, and wrap up before the session ends. It sets a natural time box for the review and keeps your local environment controlled.

Astro-Specific Tips

WireMaven works with any Astro project regardless of mode:

SSR mode (with an adapter): Your dev server handles server-side rendering. WireMaven tunnels astro dev just like it tunnels the static build preview. API routes and server endpoints work because WireMaven proxies all HTTP traffic.

Static mode: Use astro preview after astro build to share the exact static output. This is the most common pattern for content sites and marketing pages built with Astro.

Hybrid mode: Set output: 'hybrid' in astro.config.mjs and WireMaven tunnels whichever endpoints you configure. Static pages and server routes both work through the tunnel.

No special configuration is needed for any mode. WireMaven detects your Astro server port and proxies everything transparently.

Share It Before You Ship It

astro preview is great for checking your own work. WireMaven makes it great for sharing that work with others. You skip the deploy cycle, get a temporary encrypted URL, and see exactly what your reviewer sees as it happens.

The next time someone asks “can I see what you are working on?”, you have an answer that does not involve committing, pushing, and waiting.

npm install -D wiremaven