Afterlane is built around a simple workflow: define the production app you care about, tell it which routes matter, and run browser checks after deploys. The docs are organized around that flow so you can get to a useful first run quickly.
Start here
- Getting started for the fastest path from zero to a passing first check
- Projects for base URL, route list, and project detail tabs
- Webhooks for CI-triggered deploy verification
- Runs for screenshots, failures, and route-level reports
Quick path
- Create a project with a public base URL.
- Add one or more routes that matter after deploy.
- Run checks manually first so you can validate coverage.
- Wire the deploy webhook into your CI.
- Add Discord alerts once the baseline flow is working.
Common destinations
- Alerts explains project-level and default Discord webhook setup.
- Billing covers project, route, and run limits.
- Troubleshooting covers blank pages, redirect loops, and missing alerts.