Vercel 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. Every preview deployment gets verified.
- Preview deploysA preview deployment on Vercel, on every commit. Nothing waits on IronBee.
- Change analysedIronBee reads what the commit changed and decides what to check.
- Driven in a real browserAgainst your real backend, on the exact build. Watch it live in the Console.
- Verdict on the deploymentUnder Deployment Checks, with the fix on the line. On the pull request too.
Install the integration once. From then on every preview deployment is verified before anyone reviews it, and the evidence lives in the Console.
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.
The build is done and the preview has a URL. The check is waiting for its turn.
IronBee is driving the preview. The duration counts up on the deployment, and the link opens the live run.
The verdict lands on the deployment with the evidence behind it, and on the pull request when GitHub is connected.
Open the check and the run is right there
The check on the deployment links to the run. While it is going the session streams live: every action as it executes, the browser view, and the network requests behind it. When it ends, the recording replays the exact same workspace, action by action, with the verdict under it.
Your cart
Order summary
✓TARE10 appliedSubtotal$42.00Coupon (TARE10)-$4.20Shipping$9.00Total$46.80CheckoutPercent coupons discount the full amount in Stripe
lib/coupons.ts divides by 10 instead of 100, turning every percent coupon into an effective 100% off. The cart shows -$4.20, but the real Stripe Checkout session for TARE10 was created for $0.00.
- Where
lib/coupons.ts · applyPercent- Proof
- screenshot 8 · step 22
- Impact
- Every percent coupon ships the order for free.
The displayed total does not match the amount charged
With no coupon the cart shows a $9 shipping line and a $51 total, but checkout charges $42. The amount shown to the customer no longer matches the amount taken.
The preview deploys
Vercel builds exactly as before. Nothing waits on IronBee and no workflow file is added to your repository.
The check starts
IronBee appears under Deployment Checks as its own entry and runs against that deployment, at its own URL.
The change is driven
IronBee reads what the commit changed, works out what needs checking, and exercises it in a real browser against your real backend.
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.
Three connections, all from Settings → Integrations in IronBee.
Install the Vercel integration
Authorize once and pick the projects to cover. Auth and billing stay on Vercel.
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.
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_SECRETThe 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