Integrations · Deploy targets
Signed deploy notifications tell Aspian what went live. Lock auto-publishing and Aspian publishes only approved deploys.
Control levels
1Observe
We watch, record and flag.
Signed (JWS) deploy notifications, checked against approved changes.
2Gate
The tool waits for an approval.
Auto-publishing locked; Aspian publishes the approved deploy. A build plugin can also fail unapproved builds.
3HoldRecommended
Only Aspian holds the credentials.
Aspian holds the deploy token and publishes approved, prebuilt output.
Set it up
- 1Connect your Netlify team.
- 2Lock auto-publishing on production sites.
- 3Let Aspian publish approved deploys.
Limits worth knowing
- A build plugin runs inside your own build, so on its own it is a weak gate. We recommend locked publishing or Hold.
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.