
A watchdog for cron jobs and unattended AI agents: it alerts when a run is missing, stalled, failed, over its cost cap or finished without evidence, and proves every run it passes.
A startup from the Netherlands.
This page is designed to help you find out whether RunVouch is good and if it is the right choice for you.
RunVouch watches cron jobs and unattended AI agents and tells you whether they did the work, not just whether they pinged.
It raises an alert on:
On a paid plan the cost cap also brakes: the next run is refused instead of billed, so a loop that bills by the token stops instead of running until morning.
Every finished run is hashed into a leaf, every day of leaves into a Merkle root, chained to the day before it and stamped into Bitcoin with OpenTimestamps. A run report therefore cannot be edited afterwards, not by the customer and not by us, and anyone can recompute those hashes in a browser without an account and without running our code.
Teams that run jobs for clients can give each client its own public status page: that client's jobs, the last run and the 90-day record, and nothing else.
The client is a single Python file with no dependencies that wraps any command, and it fails open: monitoring can never break the job it watches. Integrations for Claude Code, OpenClaw, n8n, GitHub Actions, cron, systemd, Slack, Telegram, PagerDuty and a remote MCP server, plus a JSON API.
Free for 3 agents with all detectors and every alert channel. Solo is $19 a month for 50 agents, Team $99 for 1000 agents and the client status pages. MIT licensed, and the whole thing is self-hostable: one server file, one client file, one proof module.
Listed in
Evidence check
A run that reports success without the file, URL or assertion it promised raises NO_EVIDENCE instead of passing.
Detectors
Eight: MISSED, STALLED, FAILED, NO_EVIDENCE, RETRY_STORM, BUDGET_RUN, BUDGET_DAY, DRIFT. All of them on the free plan.
Verifiable run proof
Every finished run is hashed into a daily Merkle root, chained to the previous day and anchored in Bitcoin with OpenTimestamps.
Independent verification
Anyone can recompute the hashes in a browser or with a 90-line standard-library Python script. No account, none of our code.
Cost and token caps
Alerts on a run or an agent that goes over its budget in dollars or tokens, per run and per day.
Alert channels
Email, Telegram, Slack, webhook, and PagerDuty incidents on the Team plan.
Client
One Python file, no dependencies, wraps any command. Fails open, so monitoring can never break the job it watches.
Integrations
Claude Code plugin, OpenClaw, n8n, GitHub Actions, cron, systemd, a remote MCP server and a JSON API.
Self-hosting
MIT licensed. One server file, one client file, one SQLite database.
Two things no other watchdog in this category does. First, evidence: RunVouch does not accept a run's own word for it. If a job reports success but the file, URL or assertion it promised is not there, that is an alert, not a green tick. Second, proof: every finished run is hashed into a leaf, every day of leaves into a Merkle root, chained to the previous day and anchored in Bitcoin with OpenTimestamps. A run report cannot be edited afterwards, not by the customer and not by us, and anyone can recompute the hashes in their own browser without an account.
Choose it if your jobs are unattended and their output matters: AI agents, scheduled scrapers, nightly reports, anything where a silent success is worse than a loud failure. RunVouch is built around cost caps, retry storms and evidence, which are agent problems rather than server problems, and it gives you a proof per run you can hand to an auditor.
Where the others are better: if all you need is a ping when cron did not fire, Healthchecks.io is free, open source and excellent at exactly that. Cronitor has deeper scheduling analytics. We say so on our own comparison pages.
Developers and small teams who run work that nobody watches: cron jobs, Claude Code routines, headless agents, n8n workflows, CI schedules and backups. Typically one person responsible for dozens of jobs, who found out days later that one of them had quietly stopped. A second group is audit and compliance: teams that have to show what an automated system did, not just claim it.
It was built for our own fleet. We run dozens of scheduled jobs and unattended agents for a data products business, and the failures that hurt were never the loud ones. A job that crashes sends a stack trace. A job that finishes in four seconds instead of forty, writes nothing and reports success is invisible, and you find out when someone downstream asks where the data went. Existing monitors could only tell us a job had pinged. So we started recording what a run actually produced, and then hashing it so the record could not be quietly corrected later. RunVouch still watches that fleet every night.
Python and FastAPI on SQLite, deliberately small: one server file, one client file, one proof module. The client is standard library only and has no dependencies, so it can wrap any command anywhere Python runs. The proof chain uses SHA-256, Merkle trees and OpenTimestamps for the Bitcoin anchor. No frontend framework. MIT licensed and self-hostable.
We have collected here some useful links to help you find out if RunVouch is good.
Check the traffic stats of RunVouch on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of RunVouch on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of RunVouch's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of RunVouch on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about RunVouch on Reddit. This can help you find out how popualr the product is and what people think about it.
Do you know an article comparing RunVouch to other products?
Suggest a link to a post with product alternatives.
Is RunVouch good? This is an informative page that will help you find out. Moreover, you can review and discuss RunVouch here. The primary details have been verified within the last quarter. So they could be considered up to date. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.