Integrations · Deploy targets
Keep deploying on Vercel. Aspian watches every deployment, holds production behind Deployment Checks, and can hold the only production token.
Control levels
1Observe
We watch, record and flag.
Signed webhooks for every deployment.* event, matched against approved changes within seconds.
2Gate
The tool waits for an approval.
Deployment Checks: production promotion waits for the Aspian check to pass.
3HoldRecommended
Only Aspian holds the credentials.
Aspian holds the only production token and runs vercel deploy --prebuilt for approved output built in your CI.
Set it up
- 1Install the Aspian integration on your Vercel team.
- 2Map each project to its repo and business service.
- 3Turn on the Aspian Deployment Check for production, then move to Hold when you are ready.
Limits worth knowing
- Vercel’s Force Promote bypasses Deployment Checks. Aspian watches for deployment.promoted with no approval and treats it as a violation. Hold closes the gap.
- Vercel builds the code itself and exposes a deployment ID, not an artifact digest. Full provenance needs a CI build, an attestation and a prebuilt deploy.
More deploy targets
See what shipped without approval in your last 90 days.
Install the GitHub App and the scan arrives in minutes: every repo scored, every unreviewed merge and unapproved deploy named. Nothing is blocked until you choose.
Ship like a startup. Prove it like a bank.