Agentic deploys / Monitoring and observability
Healthchecks
Know when a cron job stops running, before your customers do.
One-liner deploy
curl -fsSL https://redu.cloud/i/healthchecks.sh | shArchitecture
£0.045/hr · delete any time
healthchecks/healthchecksby Pēteris Caune
Refhealthchecks@v4.3AuthorPēteris Caune
monitoringcronuptimealertingfree trial
Or step by step
claude mcp add --transport http redu https://mcp.redu.cloud/mcp --client-id redu-mcp
curl -fsSL https://redu.cloud/i/healthchecks.md -o redu.md
claude "Read redu.md and deploy Healthchecks on redu."About
- Each check gets an unguessable ping URL; your job curls it, and silence past the deadline raises an alert.
- One container runs the web app, the alerting daemon and the reports daemon, so a single service really is the whole product.
- Checks, ping history and accounts live in a managed Postgres on its own private VM. Nothing durable touches the container filesystem, so there is no volume to lose.
- Alerts go to email, Slack, Telegram, ntfy, Gotify, Matrix, webhooks and about thirty more, from infrastructure that is not the one you are monitoring.
Docs and links
This page deploys Healthchecks into your own redu account , from healthchecks/healthchecks at ref healthchecks@v4.3, unmodified. You run and operate the resulting instance; redu provides the infrastructure it runs on and never operates it for you.
Healthchecks is published by its own authors under BSD-3-Clause, which governs your use of it. redu is not affiliated with, endorsed by, or sponsored by the Healthchecks project. All trademarks belong to their respective owners.