See it in the dashboard
Install once in the application shell
Load the SiteAirbag script from the root layout or another stable shell so client-side navigation does not create duplicate runtime instances. Use the exact script URL and site identifier generated for the workspace.
The public installation fixture verifies a Next.js/React-rendered action as of 14 aug 2026, and in-page steps in client-rendered applications are covered as of 16 sep 2026. Custom component behavior and content-security policy still require a deployment-specific test.
Select the rendered action
Configure the real rendered button, link or form on the authorized production origin. Prefer stable semantic attributes and labels over generated CSS class names. Re-run setup after a material redesign or selector change.
Define healthy progress
Healthy evidence can include a confirmation element, a safe route change or a minimized successful network signature. SiteAirbag does not need the original form body, the values typed, page HTML or a session replay.
Protection becomes ready only after enough healthy observations and continues adapting from recent healthy behavior. Confirmed failures do not become the healthy baseline.
Test client and server failure paths
Verify normal success first. Then use an approved test environment to simulate a blocked route, provider failure or non-interactable action. Confirm that the original Next.js code remains in control and that an eligible backup appears only under the expected evidence.
Verify before relying on it
Test the original action and configured backup on desktop and mobile after installation and after material site changes. Review the coverage page, installation instructions, and security model. SiteAirbag is a fail-open recovery layer, not a guarantee that every failure is detectable or every request becomes a business outcome.