Made for humans and agents
The data didn't arrive. Nobody told you.
Describe the delivery the way you'd say it out loud - every weekday by 07:00, or just once, by Friday. We watch, and you get one alert when it doesn't arrive - and one when it does.
try one:Create monitor
API endpointwatching the connection you name nextdue every houryour monitor, as we read it
Set up in two minutes. 3 monitors free - no credit card, nothing to install on the sender's side.
AI reads your sentence once, at setup. The watching itself is plain code.
AI reads your sentence once, at setup. The watching itself is plain code.
While you were asleep
sweep interval 60s
02:58Quillstone partner SFTP droparrived4.2 MB
03:12Wrenfold nightly sales CSVlate3 min of grace left
03:15Wrenfold nightly sales CSVmissedalert sent
05:07Auditor's year-end packarrivedwatched once - finished
06:00Payroll bank return fileduewaiting
Wherever it lands, one question
Wherever the delivery lands, we only ever ask: did something new arrive inside the window?
Object stores
Amazon S3, Google Cloud Storage, Azure Blob. Nightly dumps, exports, warehouse feeds: point us at the folder, and if the day's file isn't there on time, you hear about it.
SFTP
A folder on a server you or a vendor runs. We pin the host key.
Databases and lakehouses
Postgres, Snowflake, Databricks. The table a pipeline should write to - we watch a timestamp column for fresh rows, read-only, and never touch the data.
Google Drive
Sign in read-only and we watch the folder. For the partner who works in Drive.
MCP
We call a tool on your MCP server and check its answer carries a fresh timestamp. Built for agent pipelines.
API endpoint
Poll an endpoint for a fresh status - a job reports, we check the report arrived.
Any URL
A public file or page - we watch when it last changed.
Email
Forward the report to an address we generate. Match on sender or subject.
Webhook
Anything that can send an event posts to a URL we give you. Filter on one field, or count them all.
Heartbeat URL
For jobs you do control: your script calls a URL when it finishes. If the call never comes, we tell you.
How it works
01Tell us what should arrive
One sentence - where it lands, and when: on a schedule, or just once.
"The agent drops its research report in S3 by 06:00 daily"
02We watch
Every window gets a look, day and night. If we can't see, we say so - never a false miss.
03Alert a humanone alert per miss
Missed: Stock feed04:41
04Tell an agenta straight answer
"Did it arrive?"Yes - 18:04
Or watch for it just once
Not everything repeats. The auditor's pack is coming "sometime this week". A migration's first file should land within days.
Give it a deadline instead of a schedule - we tell you the moment it lands, or once if the deadline passes with nothing. Then the monitor is finished, and says so.
Agents use it the same way: an agent that kicks off a long job can set a watch on the result, and ask later whether it came. Still at most two messages, ever.
Auditor's year-end packonce
WhereLarkfield SFTP · /inboundDeadlineby Friday 17:00 EST - a rough one is fineTell youthe moment it arrives · if the deadline passes
Arrived Thursday 09:12 - 32 hours earlyfinished
One alert, then it's done.