Expected state missing
The journey never reaches the configured success condition.
FailedJourney, evidence, outcome
Browser monitoring that proves the journey works — not just a 200 response.
PageLantern runs hosted Playwright checks through login, checkout, search, and dashboard flows, then keeps screenshots, traces, and console output with the result.
Evidence captured
Screenshots, trace, and console output stay attached to the run.
CapturedJourney recovered
A later run reaches the expected state again.
RecoveredExecution and evidence
Run the journey, then keep what responders need.
Hosted Playwright checks exercise the browser flow and preserve failure evidence without asking your team to operate browser workers.
Hosted execution
Exercise the customer-facing path.
- Hosted Playwright infrastructure
- Login, checkout, search, and dashboard flows
- Configured journey success state
Failure evidence
Start triage with the broken run.
- Screenshot, trace, and snapshot artifacts
- Console capture and signed artifact URLs
- Incident and recovery context
Plan access: Browser checks are paid: Starter includes 250 browser-check minutes a month and Team includes 1,000.
Example result
The page loaded. The checkout still failed.
Illustrative values show how the failed step and captured evidence stay connected.
- Journey
- Checkout
- Steps
- 7
- Expected state
- Order confirmation
- Screenshot
- Captured
- Console
- 1 error
- Outcome
- Failed at payment submit
Next step
Prove the journey before customers find the break.
FAQ
Frequently asked questions
How is a browser check different from an HTTP check?
Browser checks drive real journeys — login, checkout, search, dashboards — in a hosted Playwright browser, confirming the flow reached its expected state instead of only checking that a URL returns 200.
What evidence is captured when a browser check fails?
Each run can capture screenshots, traces, and console output, and those artifacts attach to incidents so responders start triage with what actually broke.
Do I need to run browser infrastructure myself?
No. Browser checks run on hosted Playwright infrastructure with nothing to install or scale, and recent run evidence is retained with automatic cleanup.