A scan is a photograph.
Your app keeps moving.
A monitor re-checks your live app or repo on a schedule and speaks only when something new appears. Known findings stay printed on the board; the alarm is saved for the thing that changed since the last check.
One monitor included on the free account · no card
Point it. It re-checks. You hear about change, nothing else.
A live URL or a GitHub repo. URL monitors probe the running app the way a stranger would; code monitors run the Sentinel scanner against the repo.
Weekly on the free account. Paid plans add daily, scan-on-every-deploy via webhook, and hourly at the top of the ladder.
An email when a new finding at or above your severity threshold appears. Each finding alerts once — never every week forever.
Severity is printed. Colour is spent on change.
Fourteen known criticals are a to-do list. One critical that was not there yesterday is an emergency. The board keeps the two apart, so a glance answers the only standing question: did anything move since the last check?
seatrial.io runs under one of these monitors right now.
This site is re-checked weekly by the same monitor you are reading about, and the Sentinel scanner’s own repo runs under a daily code monitor. Every finding is fixed or carries a written suppression rationale in the repo — see SECURITY.md.
“Put a monitor on this app.”
The same monitors are exposed as MCP tools, so Claude Code, Cursor, or Codex can create and list them from inside your editor — one line to install, one sentence to use.
One free. The ladder when you need more.
Pro and Team include Assay’s full verification pipeline in the same subscription — the full sheet is on one page.