Tell us what should arrive. We'll tell you when it doesn't.

Nothing to install, nothing to change on the sender's side - we watch where it lands: the folder, the bucket, the inbox. On a schedule, or just once.

What counts as on time

Every delivery gets a window, a due time and a grace period, in its own timezone - and one alert per miss, not one per check.

"Every day by 04:38 EST, with a 60-minute grace period" - as we run it:

window open - anything new countsgrace - late, not missedmissed - one alert
window opensdue 04:38grace ends 05:38

The grace period is there so a job running eight minutes late doesn't page anyone. If the file turns up after the alert, a second one says so. Weekday schedules skip weekends, and "by 7:30am Eastern" still means 7:30 the week the clocks change.

"The auditor's pack, sometime this week" - watched once, deadline Friday 17:00:

once
the window opens now - it can land any time, and early is the pointdeadline passes - one alert
watching from the moment you savedeadline Fri 17:00

We tell you the moment it lands. Either way it ends, the monitor is finished and stays quiet forever. Agents set these too: a watch on a long job's output, then "did it come?" later.

The six states of a delivery

One shape per state, before colour - readable on a poor screen and with colour-blindness.

the defaultHealthyArrived, or not yet due. We never alert.
window opensDueWe're looking. Silence is normal.
due passesLateInside grace. Still no alert.
grace endsMissedThe one alert we send.
when it lands - one closing alert, back to Healthy

Paused

You switched it off - a supplier on holiday, a feed being rebuilt. Never alerts, and says so.

Check broken

We couldn't look - a lost permission, an expired token. "We could not look" and "it did not arrive" are different facts - a broken check is never shown as Missed, and the alert says whose job it is to fix.

Where the AI stops

One model call at setup. None in the loop.

What the AI touches

Your setup sentence, once.

It fills in the same form you could fill in yourself, when you press the button - never as you type. You check every field before saving.

"The agent drops its research report in S3 by 06:00 daily"

Source
S3 · /reports
Due
06:00 daily
Grace
30 minutes
What it never touches

The watching and the alerts.

That part is plain code, and it keeps working if we switch the AI off. Ask whether something arrived and the answer is arithmetic, not a guess.

Every look through the window - plain code, no model in the loop

"Did it arrive?"Yes - 18:04

"Watch the run's output, once, by 18:00"watching

Quiet by design

Silence is the success state. No daily digests, no weekly summaries, no "everything is fine" mail. An alerting product that misses a miss has failed at its one job, so our own sweep loop is watched by an independent service and the status page is public and never cached.

Describe your first delivery

Under 2 minutes. Free for 3 monitors, no card.

Try it out
Menu