Features

PulseGuard does a small number of things and tells you plainly how each one works.

Uptime monitoring

  • ✓HTTP and HTTPS checks every 1, 5 or 15 minutes, or every 30 seconds on Agency.
  • ✓A site is up when it answers with a 2xx or 3xx status inside 5 seconds. On Pro you can ask for a status code or a word on the page instead.
  • ✓Ports, ping and heartbeats (a cron job or backup reporting in) on Pro.
  • ✓Uptime percentage and average response time per monitor and across the team.
  • ✓Maintenance windows on Pro, one-off or repeating: no alerts and no lost uptime while you work.

Incidents

  • ✓A failure is double-checked a few seconds later before it counts, so a momentary blip never wakes you up.
  • ✓An incident opens on a confirmed failure and closes on the first good check.
  • ✓Each records the cause (status code, timeout, DNS or TLS error), when it started and how long it lasted.
  • ✓A "down" alert and a "back up" alert with the downtime, for every incident.

SSL certificates and domains

  • ✓Every https:// monitor has its certificate read hourly, with no extra setup.
  • ✓A warning 14 days before expiry and another if it expires.
  • ✓Days remaining shown on the dashboard next to each site.
  • ✓Domain registrations too, on every plan: a warning 30 days before one expires.

Alert channels

  • ✓Email on every plan. Discord, Telegram and Slack on Pro, and SMS on paid plans at 8p a text, up to a monthly cap you set.
  • ✓Set up once per team; every channel receives every alert.
  • ✓A test button on each channel, so you know it works before you need it.

Status pages

  • ✓A public page for your clients or users: what is up, 90 days of daily uptime and past incidents.
  • ✓You choose which monitors appear. Visitors see their names, never their URLs.
  • ✓Included in Pro. It updates itself and goes out under your own title, at an address you choose (getpulseguard.com/status/your-name).

For agencies

  • ✓A team per client on one Agency subscription: separate monitors, alerts, status page and report, one bill.
  • ✓Status pages on your client’s own domain, with your title and no PulseGuard footer.
  • ✓A PDF report on the 1st of every month with uptime, response times and incidents, sent to you and your client.

Teams

  • ✓Monitors, incidents and alert channels belong to a team, so work is never tied to one person’s login.
  • ✓Invite people by email. Owners manage people and billing; members manage monitors and channels.
  • ✓Belong to several teams and switch between them: one per client works well.