Skip to content
Back to the index

PulseGuard

agentbuff.devUptime & status pages

PulseGate's liveness check found it on 16 Sep 2026; it has been in the index since 16 Sep 2026. How this is checked

PulseGuard is a heartbeat watchdog for cron jobs, workers, and other scheduled processes. Users create probes, send authenticated heartbeats, configure timeout thresholds, and receive Telegram alerts when expected check-ins stop.

Inferred · not functionally tested

WebCloud-managedAPI
PulseGuard preview
Visit agentbuff.dev

Overview

6 features

Purpose: Detecting silent failures when cron jobs and workers stop sending expected heartbeats.

Inferred · not functionally tested

Audience: developers and operations teams running scheduled jobs

Inferred · not functionally tested

Functions: monitoring

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: unknown · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, cloud_managed, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pulseguard.agentbuff.dev. These links do not verify the individual claims.

PulseGuard is an Uptime & status pages project. Inferred · not functionally tested: It focuses on detecting silent failures when cron jobs and workers stop sending expected heartbeats. Inferred · not functionally tested: PulseGuard is a B2B product aimed at developers and operations teams running scheduled jobs. Basis unknown · not verified: PulseGuard is available on the web and API.

Behind PulseGuard is Agentbuff Dev. Inferred · not functionally tested: Among its 6 catalogued features are heartbeat probes, dead man switch, and cron monitoring. Inferred · not functionally tested: Catalogued interfaces include a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Heartbeat probes
  • Dead man switch
  • Cron monitoring
  • Worker monitoring
  • Timeout thresholds
  • Telegram alerts

Topics: Inferred · not functionally tested

Tags
dead-man-switchheartbeat-monitoringcron-monitoringtelegram-alerts

JSON profile · Text profile · Access guide

Built with & integrations

Framework
Next.js
Hosting
VercelCloudflare
Connectors
APItelegram
Runs on
BrowserCloud-managedAPI-only
Detected from
Next.js
x-nextjs-prerender header · /_next/static/ in the HTML · __next_f in the HTML
Vercel
x-vercel-id header · x-vercel-cache header
Cloudflare
cf-ray header · cf-cache-status header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed16 Sep · 22:00 UTC
    Pulseguard By Agentbuff Dev seen via Saashub
    Source: Saashub · Open

Frequently asked questions about PulseGuard

What is PulseGuard?
Inferred · not functionally tested: PulseGuard focuses on detecting silent failures when cron jobs and workers stop sending expected heartbeats. It is catalogued under Uptime & status pages on PulseGate.
Who is PulseGuard for?
Inferred · not functionally tested: PulseGuard is a B2B product built for developers and operations teams running scheduled jobs.
What platforms does PulseGuard run on?
Basis unknown · not verified: PulseGuard runs on the web and API.
Is PulseGuard still active?
PulseGate's liveness check found it on 16 Sep 2026.
Who makes PulseGuard?
PulseGuard is developed by Agentbuff Dev.
Does PulseGuard have an API or integrations?
Inferred · not functionally tested: Yes — PulseGuard exposes a public API.

Similar projects

Closest matches by what these projects do

Submit to the index
Apps, agents and models — free, no signup.