Staging Preview Review

Review staging in the same surface as design and prod.

Vercel previews per PR auto-injected as screens, iframe live.

REVETOOL pulls Vercel preview deployments per PR and injects them as staging screens in your review surface. Compare design, staging and production side by side with the same context.

How it works

A clean workflow your team can adopt today.

1

Connect Vercel via PAT

Personal Access Token from vercel.com/account/tokens + team_id (format 'team_xxx' validated). Token encrypted AES-256-GCM server-side.

2

Auto-inject preview per PR

Webhook GitHub PR open → REVETOOL fetches the preview URL from Vercel → creates screen with env_kind=staging + label 'PR #N'.

3

Review side-by-side with design and prod

In the review surface, the same concept shows up to 4 variants: design, dev, staging, prod. Compare and decide.

Capabilities

Built for the moments your team actually needs it.

01

Vercel PAT integration

Token + team_id chiffré. Auto-disable on auth failures. UI Settings to rotate without losing data.

02

Iframe live in review

Allow-list 20+ domains (Vercel, Netlify, ngrok, Cloudflare Tunnel) bypass HEAD check. HTTP→HTTPS auto-upgrade silent for known hosts.

03

Deployment Protection awareness

Vercel Deployment Protection enabled by default returns 401 on iframe. REVETOOL detects and shows clean placeholder + 'How to enable embedding' modal.

04

Multi-axes Concept system

1 concept = N variants (device × fidelity × env_kind). Staging screen joins existing concept automatically.

Why it matters

What changes for your team.

  • QA reviews staging the same way as design — same surface, same context
  • Stakeholders see staging without needing Vercel credentials
  • AI critiques staging against the linked design and specs
  • Bug found in staging → reco created on the right concept, not lost in Slack

See it on your real product.

Book a 30-minute demo and we will run REVETOOL on your stack.