Software Alternatives & Startups

Officially verified details RunVouch

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.

RunVouch

RunVouch Reviews and Details

This page is designed to help you find out whether RunVouch is good and if it is the right choice for you.

Screenshots and images

  • Proof your scheduled agents did the job, and an alert the moment they do not //
    2026-09-11
  • Two lines around any job, eight detectors behind it //
    2026-09-11
  • Every agent with its state, last run, cost and open alerts //
    2026-09-11

Features & Specs

  1. Evidence check

    A run that reports success without the file, URL or assertion it promised raises NO_EVIDENCE instead of passing.

  2. Detectors

    Eight: MISSED, STALLED, FAILED, NO_EVIDENCE, RETRY_STORM, BUDGET_RUN, BUDGET_DAY, DRIFT. All of them on the free plan.

  3. Verifiable run proof

    Every finished run is hashed into a daily Merkle root, chained to the previous day and anchored in Bitcoin with OpenTimestamps.

  4. 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.

  5. 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.

  6. Alert channels

    Email, Telegram, Slack, webhook, and PagerDuty incidents on the Team plan.

  7. Client

    One Python file, no dependencies, wraps any command. Fails open, so monitoring can never break the job it watches.

  8. Integrations

    Claude Code plugin, OpenClaw, n8n, GitHub Actions, cron, systemd, a remote MCP server and a JSON API.

  9. Self-hosting

    MIT licensed. One server file, one client file, one SQLite database.

Badges

Promote RunVouch. You can add any of these badges on your website.

SaaSHub badge
Show embed code

Questions & Answers

As answered by people managing RunVouch.
  1. What makes RunVouch unique?

    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.

  2. Why should a person choose RunVouch over its competitors?

    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.

  3. How would you describe the primary audience of RunVouch?

    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.

  4. What's the story behind RunVouch?

    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.

  5. Which are the primary technologies used for building RunVouch?

    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.

Videos

We don't have any videos for RunVouch yet.

Do you know an article comparing RunVouch to other products?
Suggest a link to a post with product alternatives.

Suggest an article

RunVouch discussion

Log in or Post with

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.