sigabrt — know when your service stops

sigabrt

Docs
Pricing
Log in
Start free

$
ssh sigabrt.dev
Work in progress

Know the moment your service stops running.

Your script pings a URL when it finishes. If the ping doesn't arrive on
schedule, sigabrt emails you.

Start free
See pricing

10 heartbeats free. No card required.

nightly-backup — crontab

0 3 * * *
./backup.sh && \
curl -fsS https://sigabrt.dev/pulse/8f3c…/beat

nightly-backup · every 24h · 15m grace
Mon — Thu

three nights of pulses, right on time
Thu 03:15 — nothing arrived. Email sent.

01
Create an endpoint
Name it, say how often it should report in, and how long you'll forgive it. You get a ping URL.

02
Add one line to the job
A curl at the end of your script, after the work succeeds. No agent, no library, no credentials.

03
Forget about it
Silence means it's fine. You only hear from us when a pulse doesn't arrive.

In your terminal
Work in progress

Endpoints over SSH

Add your SSH public key in settings, then connect. Every endpoint’s status,
schedule and recent events in your terminal.

$ssh sigabrt.dev
Add your public key

Early days: it only reads for now, and it will change as it grows.
Tell us what you’d want from it.

ssh sigabrt.dev

sigabrt read-only · work in progress
 
STATUS NAME EVERY LAST PING
● ok nightly-backup 1d 6h ago
● ok db-dump 1h 12m ago
● grace invoice-sync 15m 17m ago
● down cert-renew 1d 2d ago
 
↑↓ select · enter events · q quit

Alerts
Email and/or ntfy on status changes

History
Pulses and status changes

Interval
From one minute upward, with a grace period

One price.

Unlimited endpoints, unlimited heartbeats, 90 days of history. Start on
the free tier and upgrade when it's carrying something you'd miss.

€15
/ month

sigabrt.dev

Docs
Pricing
Terms
Contact

The sigabrt service is designed to provide a mechanism for monitoring the runtime status of external services by detecting when a scheduled process fails to report its completion. The core functionality operates on a heartbeat system: a user's script pings a designated URL upon the completion of a task. If this expected ping does not arrive within the specified schedule, the system automatically sends an email notification to the user, effectively alerting them to service interruptions.

The process for utilizing this system involves three key steps. First, a user must create an endpoint, which requires establishing a name, defining the desired reporting frequency, and setting a grace period to allow for minor delays. This action yields a unique ping URL. Second, the user integrates this monitoring into their job by adding a single line of code, specifically a curl command following the successful completion of the main task. This setup requires no external agents, libraries, or credentials, relying purely on the script execution. Finally, the philosophy behind the system is based on the principle of silence; the user is notified only when a pulse fails to arrive, allowing them to largely disregard the system during normal operation.

The platform offers various ways for users to interact with the monitoring data. Direct access is provided via SSH, allowing users to connect to sigabrt.dev to view the status, schedules, and recent events for all configured endpoints in real time. This interface presents a status overview, listing endpoints such as nightly-backup, db-dump, invoice-sync, and cert-renew, along with their current status, schedule information, and the time of the last ping. Furthermore, the system supports alert configurations through email or ntfy for status changes, and a history log detailing all pulses and status updates is available for review.

The service operates on an interval structure that allows for granular control over reporting, spanning from one minute upward, incorporating a grace period for flexibility. Regarding cost, sigabrt offers a unified pricing structure, providing unlimited endpoints and unlimited heartbeats along with ninety days of historical data. Users can begin with a free tier and upgrade based on their operational needs, with the standard monthly pricing being fifteen euros. This structure is designed to support extensive monitoring requirements by allowing users to scale their usage as their services grow in complexity and importance.