Preview deployment ready
Vercel finishes building a preview and the IronBee check starts against that deployment, at its own URL.
TriggerVercel Integration
Install once and every preview deployment gets driven. IronBee runs as a deployment check, exercises what the commit changed, and reports back on the deployment. No workflow file, no test suite to maintain.
Connect Vercel to run these on every deployment
New commit on a pull request
Every push produces a new deployment, so every commit gets its own run rather than sharing one nightly pass.
TriggerWrite a scenario from the diff
IronBee reads what the commit changed and produces the journey that change can break, instead of replaying a fixed suite.
ActionDrive the preview
A real browser against your real backend, on the exact build under review. Clicks, forms, requests and responses.
ActionReport on the deployment
The result appears under Deployment Checks with its own duration, and links out to the run it came from.
ActionComment on the pull request
When the project is connected to GitHub, the same run is posted on the pull request with what was verified and what was found.
ActionAttach the evidence
The replay, the network payloads, the spans and the file the finding came from, all on the run rather than in a log.
ActionSuggest the fix
The diff to apply, on the line it belongs to, ready to hand to Claude Code, Cursor or Codex.
ActionOn the deployment
You can watch it happen
The check appears the moment the deployment finishes and stays on the page through the run, counting up. Opening it takes you to the run itself, step by step, as it goes.
Build Logs34sDeployment SummaryResourcesDeployment Checks
IronBee Verification4m 49sAssigning Custom DomainsSkipped
IronBee VerificationQueued
The build is done and the preview has a URL. The check is waiting for its turn.
IronBee Verification1m 12s
IronBee is driving the preview. The duration counts up on the deployment, and the link opens the live run.
IronBee Verification4m 49s
The verdict lands on the deployment with the evidence behind it, and on the pull request when GitHub is connected.
How it runs
01
The preview deploys
Vercel builds exactly as before. Nothing waits on IronBee and no workflow file is added to your repository.
02
The check starts
IronBee appears under Deployment Checks as its own entry and runs against that deployment, at its own URL.
03
The change is driven
The agent reads what the commit changed, writes a scenario for it, and exercises it in a real browser against your real backend.
04
The result comes back
Pass or fail on the deployment, with the evidence behind it: what was verified, what was found, and the files it came from.
Setup
Three connections, all from Settings → Integrations in IronBee.
01
Install the Vercel integration
Authorize once and pick the projects to cover. Auth and billing stay on Vercel.
02
Install the GitHub App
Read-only repository access, so the verification agent can check out your code during a run and see what the commit changed.
03
Add a Protection Bypass secret
If your previews are protected, add a Vercel automation bypass secret so IronBee can reach the deployment it is meant to check.
VERCEL_AUTOMATION_BYPASS_SECRETWith GitHub connected
The same run, on the pull request
If the project is connected to GitHub, IronBee posts the verification on the pull request as well: what it checked, what it found, and which files the finding came from.
IronBee Verification
Verification failed