Script Beacon landing page summary (source: https://scriptbeacon.com/)

Heartbeat & logs in one POST. Monitor cron jobs and workers, detect missed or late runs, send Slack/Email alerts, and store JSON from every run for instant search and routing.

How Script Beacon works:
1. Create a monitor, name it, and toggle a schedule whenever you want uptime checks. Cron syntax is validated, plan minimums are respected, and next due stays in your timezone.
2. Send JSON from any language to /b/<beacon-id> with top-level primitives (≤16 KB). When a schedule is enabled you can send light heartbeats like {"heartbeat":"alive"}; pure heartbeats never consume monthly log quota.
3. See events instantly, subscribe channels to DOWN/UP, and add payload-match forwarding rules to fan out matches to Slack, Teams, or any HTTPS webhook.

What teams get:
- Searchable event feed with stable keyset pagination, filters for status, event type, IP, or whitelisted payload keys, plus CSV export for bounded ranges.
- Heartbeats with honest status that compute UP, LATE, and DOWN from your schedule while anchoring uptime after the first successful run.
- Alerts where your team works by routing DOWN (and optional UP) to Email, Slack, Teams, or webhooks with per-channel cooldowns.
- Built-in reports that surface heartbeat uptime, lowest uptime, outage summaries, and ingestion trends without extra setup.
- Payload forwarding rules that match JSON with ANDed conditions (eq, neq, gt, lt, contains, not_contains) and fan-out to chat tools or webhooks with cooldown windows.

Supported ingest and fan-out tools: cURL, fetch, requests, PowerShell, Slack, Teams, and generic HTTPS webhooks.

Docs: https://scriptbeacon.com/docs
Support: https://scriptbeacon.com/support
Pricing: https://scriptbeacon.com/pricing