Watch your stack. And theirs.

Scheduled re-audits of the sites you care about - catch a new vulnerability, an end-of-life library or a version drift before it becomes an incident.

What you can watch

• Own site - your sites: vulnerabilities, certificates, drift, before they bite.
• Competitor - their stack moves and score changes.

What a watch does

• Re-audits on scheduleWatched sites re-audit automatically - daily on every paid plan.
• One event feedTech changes, version drift and score moves, plus new vulnerabilities, end-of-life technologies and certificate expiry - one timeline per site.
• Risk radarPro and up: known-exploited and high-severity advisories on your stack surfaced first, so the urgent items rise to the top.

What lands in the feed

One timeline per watched site, newest first. Every entry names what changed and on which audit it was seen, so a change is something you can look up rather than something you have to remember.

• A technology appears or disappearsA new framework, analytics tag or CDN shows up - or one you relied on is suddenly gone. On a competitor that is a decision you can read; on your own site it is often a change nobody announced.
• A version movesUp after a deployment, or quietly further behind as the library keeps releasing without you. Version drift is the slow one: nothing breaks on the day it starts.
• A new vulnerability touches the stackA published advisory that matches something the site actually runs - not a generic feed to triage yourself.
• A technology reaches end of lifeStill working, no longer maintained. This is the entry that gives you months of warning instead of an incident.
• A certificate is running outNamed with the date, while there is still time to act.
• The score movesUp or down, with the sub-score that caused it - so a drop is a lead, not a mystery.

How many sites you can watch

Watching starts on Starter. The Free plan runs on-demand audits and watches nothing - we would rather say that here than let you find it out after signing up.

• FreeNo watched sites
• Starter1 site
• Pro10 sites
• StudioUnlimited sites

Why this isn't uptime monitoring

An uptime monitor answers one question: is the site responding? That is a good question, and this is not it. Stack Watch answers a different one - what is the site made of, and what changed since the last audit?

• A site can be up all week and still get worseIt picks up a package with a published advisory, slips a version behind, or runs a technology that stopped being maintained. Every request returns 200 the whole time.
• Change monitors read the page, we read the stackTools that watch a page for changes compare text and pixels and tell you the wording moved. We look at what runs underneath - the libraries, frameworks and versions - and tell you the foundation moved.
• Use both, for different questionsIf you need to know within a minute that a page is down, use an uptime monitor. If you need to know that the page now runs a library with a published advisory, that is this.