Step 1: Create a project
Create one project per deployed app. Set a project name and a public base URL that the worker can reach.
Step 2: Add routes
Start with the routes that break first when a deploy goes wrong:
//login/dashboard- checkout or onboarding flows
If you leave the route list blank during project creation, Afterlane still creates the project with /.
Step 3: Run a manual check
Use a manual run before you automate anything. This gives you a clean baseline for:
- the routes being visited
- the screenshots being captured
- the run report structure
- any console errors or visible-content failures
Step 4: Wire deploy triggers
After the manual run looks right, add the deploy webhook to GitHub Actions or your CI so checks run automatically after successful deploys.
What Afterlane checks
Afterlane opens your routes in a real browser, looks for visible content, captures a screenshot, and records browser errors. That makes it useful for blank pages, redirect loops, hydration failures, broken JS, and other regressions that still slip past HTTP-level monitoring.