Getting started
Audit every deploy, automatically
Connect Vercel and Actuant re-audits your app after every production deploy, then tells you only what got worse.
Last updated 2026-09-03
An audit is a photograph. It was true the moment it ran, and your next deploy can undo any of it without saying so. That is how an app drifts from launch-ready back to broken without anyone noticing for weeks.
Continuous monitoring closes that gap. Actuant watches your deployments and re-audits the app each time production changes.
Connect Vercel
Open any app, go to its Settings tab, and find Audit every deploy.
- 1
Connect Vercel
You are sent to Vercel to install the Actuant integration and choose which projects it may read. Read-only: Actuant never creates deployments or changes your project.
- 2
Pick the project
Choose the Vercel project that deploys this app. The list is shown by production domain rather than project name, and the matching one is pre-selected.
- 3
Press Watch
Actuant takes a baseline audit immediately. Every deploy after that is compared against it.
Any platform
Not on Vercel? Every app also gets a plain webhook URL you can POST to from any CI step, a deploy script, or your coding agent once it has finished shipping. It starts exactly the same check.
What happens on a deploy
Three kinds of event count, because all three change what your users are served: a successful production deploy, promoting an existing build to production, and accepting a rollback. Preview deploys are ignored on purpose, since they live on throwaway URLs nobody visits.
| Step | What it does | Cost |
|---|---|---|
| Deploy lands | Vercel tells Actuant the production deploy succeeded. | free |
| Settle | Actuant waits about 90 seconds so the CDN is serving the new build, not the old one. | free |
| Fingerprint | A cheap fetch asks whether the bytes actually changed. | ~2c |
| Re-audit | Only if they did. A real browser, the full check set. | ~50c |
| Diff | The new run is compared against the previous one. | free |
| Alert | Only if something regressed. | free |
A deploy that changed nothing costs about two cents, so an app you are not actively shipping to is nearly free to watch. Pushing eight commits in twenty minutes produces one audit, not eight.
When Actuant contacts you
A regression is a check that was passing on your previous deploy and is not passing now. That is the only thing that triggers an email.
- A new critical issue is emailed immediately.
- Anything softer has to be seen twice before it reaches you, so a page that timed out once under load does not become an alert.
- A clean deploy sends nothing. Silence is the signal that nothing broke.
Why you will not hear from us often
There is deliberately no "your app was audited and everything is fine" email. A monitor that writes after every deploy is a monitor you filter, and the day it finally has something to say is the day the filter eats it.
Pausing and changing it
The same Settings panel pauses monitoring without losing the project link, changes how often a scheduled check runs, or disconnects Vercel entirely. Disconnecting removes the stored token and every project link with it.
Monitoring is available from the Launch plan up. The audit itself stays free on every plan.
Keep reading
Your first audit
How to read an Actuant launch-readiness report: what the 0–100 score means, how weighting works, and how to turn the per-check breakdown into a prioritised launch to-do list.
Launch readiness
Launch readiness is how prepared a deployed app is to actually receive, measure, and convert visitors. Learn the fundamentals every app needs before it's worth driving traffic to.