make the case
Pre-run review for the scripts we run against production.
A one-page summary to forward to your manager or change board.
The problem
Admins run scripts against production every week: from colleagues, vendors, their own library and increasingly from AI chat tools. A missing filter, an empty variable or an over-broad permission turns a one-object change into an environment-wide one, and peer review rarely catches what a script will actually reach. There is usually no consistent check before a script runs.
What ScriptPreflight produces
- A verdict and the blast radius: one object, a filtered set or everything the account can reach.
- Expected object count versus blast radius: does the script touch more than the change ticket says?
- Access needed and whether the change can be undone.
- Every finding with its rule ID, line span and engine version, so it can be attached to a change record.
See a full example: sample report (https://scriptpreflight.com/sample-report).
Cost
| Plan | Price | Includes |
|---|---|---|
| Free trial | Free | 3 full preflights, no card |
| Individual | $12 / month (R219 / month) | One admin, 40 preflights a month |
| Team | $49 / month | 5 members with roles, shared library, 250 pooled preflights a month |
Prices exclude VAT where applicable. Billing is handled by Paddle, our merchant of record.
How scripts are handled
- Scripts are never executed and we never connect to your environment.
- Common secret patterns are redacted in the browser before upload and again on the server.
- Temporary preflights are not retained; reports keep the flagged lines as evidence.
- Saved scripts are encrypted per version with keys held in Azure Key Vault.
- Your scripts are not used to train AI models.
Email you can send
ScriptPreflight · scriptpreflight.com · hello@scriptpreflight.com