What makes it different
What makes Mortemain different.
The cron and heartbeat monitoring category shares a few blind spots. Here is how Mortemain lines up against the typical monitor, on the things that are built and verifiable today.
| Capability | The typical heartbeat monitor | Mortemain |
|---|---|---|
| Dead-simple setup | A secret URL to call, no agent to install. | One preconfigured line to paste, no agent, no SDK, no config file. |
| Check-in authentication | An unauthenticated secret URL. Anyone who captures or leaks it can replay it to keep a dead check looking alive. | Optional HMAC-signed check-ins with a timestamp window, so a captured URL can't be replayed. |
| Encryption at rest | Commonly infrastructure or disk-level encryption. | Cryptographically partitioned multi-tenancy: sensitive fields encrypted with a per-account key, so a stolen database stays unreadable. |
| Flapping | Re-notification or nagging when a check keeps failing. | Dedicated flapping detection, with a single notice on genuine recovery. |
| Data residency | Frequently hosted outside the EU. | An EU business, data in France and Germany, under the GDPR. |
| Check-in transport | One HTTP request. | One HTTP request, or an email, so even a box that can't run curl can check in. |
| Pricing model | Often per-monitor or per-seat, which pushes you to ration checks. | Flat per plan, never per-monitor or per-seat. |
This compares Mortemain to common patterns across the cron and heartbeat monitoring category, not to any single product.
See it for yourself.
Mortemain is in private beta. Join the waitlist and lock in founding pricing.