Skip to main content

Watch

Watch re-checks the public page of an app in your Watch slot: uptime, HTTPS, verdict, speed, and functional page shape. Free is about once a day. Pro is about every hour. Business matches the 15-minute scheduler. Not 5 seconds, and not PagerDuty.

If a check looks like a deploy flap (down, broken same-origin assets, empty shell, or a WAF block), Watch retries up to three times in that tick with a few seconds between tries. It does not sleep for three minutes per app. Two consecutive downs are still required before an uptime email. A WAF unknown result is not emailed as Down.

What Watch can see

  • The public URL you added
  • Response time and whether the page answers
  • Verdict moving between Ready / Fix first / Do not launch
  • A speed jump (about 2x and over 400ms, or a 500ms jump) when that switch is on
  • A functional page break: vanished title, vanished forms, or most of the HTML gone. Hashed Tailwind or bundle class names are ignored. This is static HTML from a GET, not a headless wait after hydration.

What Watch cannot see

  • Other people’s logins
  • In-app exceptions, unless you also install an SDK on a connected project and turn on the Watch switch for visitor errors

Email and chat

You get a bell notice, and an email when that public surface moves. Email needs transactional mail configured on the Invince host. You can also paste a Slack Incoming Webhook or a Discord webhook on Watch. Invince does not call PagerDuty, phone, or SMS.

Turn product emails off in Profile except security-required mail.

Free includes 1 Watch slot.

Badge and JSON

  • SVG: /api/badge/{id}
  • JSON: /api/badge/{id}/status (verdict, working, HTTPS, response time, checkedAt). Only for a check you own.

We use only the cookies necessary to keep you signed in. No analytics or advertising cookies are set. Cookie list