A check on each preview link
Start it from CI, from Cursor or from the dashboard. Every report ends up in the same list.
For teams
If your team ships several apps a week with AI tools, nobody has time to look at every page on a phone. We check each release and send the list to whoever shipped it.
Talk to us about my teamStart it from CI, from Cursor or from the dashboard. Every report ends up in the same list.
The intern's weekend app and the main product get the same contrast, layout and wording checks.
Paste the list into the tool, ship the fix, and we check again to confirm it worked.
Your pages and reports are not used to train any model.
We open public pages in a sandboxed browser. We never write anything to your app.
Make or revoke API keys whenever you like. We store only a hash of each key.
No. We use the pages you submit only to run the checks you ask for and show you the results.
No. We send findings. Your team or your AI tool makes the change, after someone on your side says yes.
Public URLs only for now, and that includes Vercel and Netlify preview links. If your staging is behind a login, tell us how it’s set up.
Yes. Call the HTTP API from CI, or connect Cursor or Claude Code over MCP. You make API keys in your dashboard.
The link, the screenshots and the findings, so you can open a report again later. The Privacy Policy has the details.