What PulseGuard Does
PulseGuard continuously sends checks from its global probe network to your endpoints at intervals as short as 30 seconds. When a check fails, PulseGuard uses a double-check protocol — it retries from an alternate vantage point before declaring downtime — so you get accurate alerts without noise. Every result feeds into real-time latency charts and uptime reports that help you understand trends, not just point-in-time failures.Core Capabilities
Monitor Types
PulseGuard supports 16 monitor types, so you can watch every layer of your stack:
Monitors run at configurable intervals from 30 seconds to 24 hours. For each monitor you can define expected status codes, response body assertions using JSONPath or regex, and per-monitor alert thresholds.
Global Probe Network
Checks run from 50+ locations across North America, Europe, Asia Pacific, South America, Africa, and the Middle East. You choose which regions to include per monitor, giving you fine-grained visibility into where your service is healthy and where it isn’t.Alerting Channels
When a monitor changes state, PulseGuard notifies your team through the channels you already use:- Email — fully templated with incident context
- Slack — interactive blocks with one-click acknowledge
- Discord — rich embeds with severity colors
- Webhook — POST to any endpoint with a structured JSON payload
- Telegram — instant bot messages
- SMS — text alerts for critical on-call scenarios
Incident Management
Every alert opens an incident with a structured lifecycle:Investigating → Identified → Monitoring → Resolved. You can attach a post-mortem to any incident, recording the root cause, a corrected timeline, action items, and severity level.
Public Status Pages
PulseGuard generates a public status page for your organization with no extra setup. You can add a custom domain, password-protect the page, schedule maintenance windows, and let visitors subscribe to per-monitor email updates. Pages support custom CSS, custom JavaScript, favicons, OG images, and multi-language (i18n) content.Private Probes
For services that live inside a private network — internal APIs, staging environments, database hosts — PulseGuard provides Docker-based private probes. You deploy a lightweight agent container in your infrastructure, and it polls PulseGuard for check jobs, executes them locally, and reports results back. No inbound firewall rules required.CLI and Monitoring as Code
Thepulse CLI lets you manage your entire monitoring configuration from version-controlled YAML files:
REST API
Every resource in PulseGuard is accessible over a REST API secured with scoped API keys. You can create monitors, query check results, manage alert channels, and inspect incidents — all programmatically. See the API Overview for endpoint details.Plans and Limits
PulseGuard is designed to scale from side projects to enterprise deployments.The check budget on the Free plan counts every individual probe execution. A single monitor running in 3 regions uses 3 checks per execution cycle.
Next Steps
Quickstart
Create your first monitor and view live results in under five minutes.
Monitor Types
Explore all 16 monitor types and their configuration options.
Alerting
Configure notification channels and incident workflows.
Status Pages
Publish a public status page for your users.
CLI
Manage monitors as code with the
pulse CLI.API Reference
Integrate PulseGuard into your own tooling via REST.