Know the moment
something breaks.
HeimPulse checks your endpoints on a schedule, turns repeated failures into incidents automatically, and publishes a status page your customers actually read — without the setup tax of the incumbents.
No credit card to start
Partial outage · Checkout — elevated 5xx
Aug 14 · resolved in 12m
Everything between "it's down" and "customers know."
Seven things, done properly, instead of forty things done half-way.
Uptime monitoring
HTTP checks on the interval you choose, from Frankfurt and New Jersey — more regions on request. Assert on status code, latency, headers, or response body — see exactly what failed, not just that something did.
HTTP · status · latency · headers · body Learn more →Status pages
A page your customers bookmark instead of emailing you. Your logo, your domain on paid plans, live incident history.
Learn more →SSL monitoring
Add a host, set your own warning threshold, and get a real TLS handshake result on a recurring schedule — before an expired cert becomes a Monday-morning surprise.
Learn more →Incident monitoring
Consecutive failures open an incident automatically, using a failure-count and time-window you set per service — and it closes itself when the service recovers. Already know what's going on? Post the update yourself instead.
auto-detect · per-service thresholds Learn more →Notifications
The moment a check fails or an incident opens, HeimPulse tells the people who need to know — a signed webhook, a Slack message, or an email — retrying automatically until delivery actually goes through.
webhook · Slack · email Learn more →Programmatic API
Manage services and incidents from a script, CI pipeline, or your own infrastructure-as-code tooling — org-scoped API keys and a full reference at docs.heimpulse.com.
REST API · API keys · OpenAPI spec Learn more →MCP monitoring Beta
Uptime and latency for your MCP server, same as any endpoint — plus schema-drift detection that catches a renamed tool or a changed input shape before an agent silently breaks on it.
initialize · tools/list · schema fingerprint Learn more →Start free. Grow into it.
Three plans, real limits, no surprise seats.
For small teams and side projects getting started.
- —3 services, 3 endpoints each
- —5-minute minimum interval
- —1 region (your choice)
- —1 status page
- —3 team members
- —1-day check logs
- —Email alerts
- —"Powered by HeimPulse" watermark
- —No custom domain
- —No SSL certificate monitoring
- —No MCP schema-drift monitoring
- —No webhook/Slack alerts
For growing teams that need full regional coverage.
- —25 services, 10 endpoints each
- —1-minute minimum interval
- —All regions
- —3 status pages
- —10 team members
- —7-day check logs
- —Remove the watermark
- —Custom domain
- —Email alerts
- —SSL certificate expiry monitoring
- —MCP schema-drift monitoring Beta
- —Webhook & Slack alerts
For organizations that need SSO, APIs, and compliance.
- —100 services, 25 endpoints each
- —30-second minimum interval
- —All regions
- —25 status pages
- —50 team members
- —14-day check logs
- —Remove the watermark
- —Custom domain
- —Email alerts
- —SSL certificate expiry monitoring
- —MCP schema-drift monitoring Beta
- —Webhook & Slack alerts
- —Single sign-on (SSO)
- —Programmatic API access
Not sure where to start?
See HeimPulse organized by the specific problem it solves, not the feature list.
Browse solutions → Considering something else?Honest comparisons, not a pitch
What tools like Uptime Kuma and Datadog actually do well, and where HeimPulse fits instead.
See alternatives → Hit an error?What it means, and whose problem it is
Plain-language explainers for 502s, 504s, connection failures, and DNS errors — plus a real diagnostic checklist if you run the service.
Browse error explainers →Set it up before your coffee's cold.
Add your first endpoint, pick an interval, and HeimPulse starts watching.