Test public Vercel, Netlify, and Cloudflare Pages previews

You do not add a customer workflow file or connect a separate provider account. Verisual listens to its signed GitHub App webhook and recognizes successful preview signals from Vercel, Netlify, and Cloudflare Pages.

The installation needs Deployments and Commit Statuses read access, plus the existing Checks read/write access. Older installations show a reauthorization notice until a workspace owner or admin reconnects the app with those permissions.

Verisual uses deployment-status events for Vercel, commit-status events for Netlify, and check-run events for Cloudflare Pages. For custom preview domains, the authenticated GitHub app or status context matters; a hostname suffix alone does not.

1. Save an approved default target for the project.
2. On Free, choose Try PR previews to start the one-time evaluation before validation.
3. Create a zero-model YAML journey or save an existing public journey.
4. Validate and activate the journey.
5. Choose which active journeys should run for PR previews.
6. Enable PR previews.
7. If prompted, review and approve the default target setup run.

The project locks to the first recognized provider and successful status context. Later signals from other providers are ignored until an owner, admin, or developer resets the source. Before execution Verisual requires exactly one open PR for the signal SHA and rechecks that the SHA is still the current PR head.

The execution URL is the detected preview, but comparison uses the approved manifest for the default target. A preview run can never replace that default target.

Free starts one 14-day, 30-minute evaluation when Try PR previews is first selected. Those minutes can be used only for journey validation, default target setup, and PR preview runs. The grant cannot be restarted. Free runs never call an AI model.

Starter preview runs use the included 300 hosted minutes per billing month; Pro uses the included 1,500. Downgrading stops new hosted runs when no evaluation or paid pool is available, while saved settings, retained results, and Playwright export remain accessible.

• Protected preview: make the preview public; v1 sends no bypass credential.
• Stale SHA: wait for the provider to deploy the current PR head.
• Provider lock: reset the source, then let the intended provider report the next successful preview.
• Baseline required: approve the default target setup run.
• Quota exhausted: wait for the paid pool to reset or upgrade; the one-time Free grant does not repeat.
• Reauthorization required: reconnect the GitHub App with Deployments and Commit Statuses read access.