How long can an async review stay open?

A session lasts 15, 30, or 60 minutes. Pick the shortest window that gives reviewers enough time.

Do reviewers need to stay on a call?

No. They open the URL on their time. You still see viewer and request activity in the popup's session log.

What happens after expiry?

The relay URL stops serving the local build. Reviewers see an expired-link page.

Is async review a replacement for release signoff?

No. Use it for feedback on in-progress local work. Keep release signoff in your normal release process.

Async Reviews

Send a short-lived link and read the session trail.

Share the local build for a set window. Reviewers click through on their time while you see joins, requests, failures, and expiry.

Get the Chrome extension All use cases

How it works

Three steps. One review window.

Start from the build in front of you, share a scoped link, and keep the session visible while reviewers click through.

Choose the window

Pick 15, 30, or 60 minutes in the wiremaven extension before you share the link.

wiremaven popup

▶port 3000 · session 60M · Start

connected

link: relay.wm/p/async-review

expires: 60M · session log: on

Send the review link

Post the relay URL in Slack, Linear, or the PR. Reviewers open it when they have time.

Read the session trail

Viewer events and request outcomes show what reviewers touched before access closed.

Why wiremaven

Async review should still leave a trail.

A local link in chat can disappear into the day. wiremaven gives the review a clock, an access boundary, and enough session context to act on feedback.

Calendar

Review without a meeting.

Send the link when a live walkthrough would slow the team down.

Boundary

Access closes on schedule.

Pick the expiry before you share. The link stops working when the feedback window ends.

Signal

The session shows activity.

Use viewer and request events to understand who reviewed the build and what they touched.

Momentum

No deploy chore.

Share the build running on your machine instead of waiting for a preview environment.

The shift

From loose links to time-boxed review sessions.

Before

Review links sit open in chat
The team cannot tell who opened the build
Feedback arrives without route context
Local work waits for preview deploys
Access stays live after the review

After

The link matches the feedback window
Viewer events show who joined
Request outcomes give feedback context
Review starts from the local build
Expiry closes access at the end

What you get

Async review without losing control.

Timed

Expiry-first sharing

Set the review window before the URL leaves your machine.

Traceable

Session activity

See joins, route requests, failures, and timing while reviewers click through.

Simple

No reviewer setup

Reviewers click the URL. They do not need a repo, account, or local environment.

Focused

Local build review

Share the exact work you need reviewed before it reaches staging.

Safe

Encrypted relay

Traffic goes through wiremaven's relay while your local server keeps its inbound ports closed.

Clean

Expired-link page

Reviewers see a clear expired state after the window closes, not a raw transport error.

Start here

Send the next review link with a clock on it.

Open a tunnel, set the expiry, and use the session trail when feedback comes back.

Read the docs

FAQ

Common questions

How long can an async review stay open?: A session lasts 15, 30, or 60 minutes. Pick the shortest window that gives reviewers enough time.
Do reviewers need to stay on a call?: No. They open the URL on their time. You still see viewer and request activity in the popup's session log.
What happens after expiry?: The relay URL stops serving the local build. Reviewers see an expired-link page.
Is async review a replacement for release signoff?: No. Use it for feedback on in-progress local work. Keep release signoff in your normal release process.