PulseTrace
Start free
Features

Everything PulseTrace does, one page each.

Fifteen capabilities, each with how it works, which plan has it, and the monitor types and integrations it pairs with.

Detect

Availability

Uptime monitoring

Know an endpoint is down before a customer tells you.

Explore APIs

API monitoring

An API that returns 200 with the wrong body is still down.

Explore Synthetic API

Multi-step API checks

Real user flows are sequences: authenticate, create, read back, clean up.

Explore DNS

DNS monitoring

Resolve a name from every region, assert the answer you expect, and get told the moment a record changes.

Explore Probe fleet

Multi-region checks

Where a check runs from decides what it can see.

Explore

Secure

TLS

SSL certificate monitoring

Expired certificates are the most avoidable outage there is.

Explore HTTP security

Security headers grading

HSTS, CSP, X-Frame-Options, cookie flags, CORS policy: the controls that stop whole classes of attack, and the ones that quietly disappear after a deploy.

Explore Domain security

Domain expiry & DNSSEC monitoring

The domain is the one dependency everything else hangs off.

Explore

Understand

Intelligence

Change detection

Most incidents start with a change nobody announced.

Explore Intelligence

Anomaly detection

Thresholds are guesses that go stale.

Explore Incidents

Incident management

A failing check becomes an incident the moment it trips your rule — debounced against flapping, grouped with related failures, assigned, acknowledged and resolved with a full audit trail, and mirrored to PagerDuty, Opsgenie, incident.io or Rootly if that's where your process lives..

Explore

Prove & govern

Communicate

Status pages

Pick the monitors, choose a slug or your own domain, and the page updates itself: 90-day uptime bars, open incidents, maintenance windows.

Explore Reporting

SLA reporting

When a customer asks for last quarter's uptime, the answer should take a click.

Explore Governance

Environments

Staging noise shouldn't page production on-call, and a developer's API key shouldn't be able to touch production monitors.

Explore Governance

Roles, service accounts & audit log

Four roles (owner, admin, developer, viewer), API keys with explicit scopes, expiry and IP restrictions, service accounts for automation that outlive any one person, and an audit log of who changed what — so a monitoring platform with production credentials in it is governed like one..

Explore

See them on your own endpoints.

Ten monitors, one region and a status page are free forever — no card, no sales call.

Start monitoring free Compare plans