Building a Reliable Cron Job Heartbeat Monitor with NestJS and SQLite

How We Built a Cron Job Monitoring System That Actually Works

QuietPulse is a heartbeat monitoring system designed to detect silent failures in background tasks. It operates on a single $4/month DigitalOcean VPS and utilizes Telegram for immediate failure notifications. The system records successful pings via a simple GET request and alerts users if a job doesn’t check in on time.

Why This Matters

In modern SaaS architecture, cron jobs are critical but often lack visibility, leading to silent failures that aren’t discovered until data corruption or service outages occur. While many engineering teams reach for complex, high-cost observability stacks, the technical reality is that a simple stateless heartbeat endpoint can provide 100% visibility into task execution.

By leveraging a minimalist stack consisting of NestJS, SQLite in WAL mode, and Telegram, developers can achieve production-grade reliability without the overhead of Kubernetes or microservices. This approach prioritizes immediate alerting over complex analytics, addressing the core engineering need: knowing if a job ran when it was supposed to.

Key Insights

• NestJS and SQLite with Prisma ORM can handle thousands of pings per minute when using Write-Ahead Logging (WAL) mode (QuietPulse, 2026).
• Stateless heartbeat monitoring via unique GET request tokens allows for job tracking from any environment with outbound internet access.
• Telegram Bot API serves as a more reliable instant notification channel than traditional email for developer alerts.
• NOWPayments integration allows for global SaaS operations in regions where Stripe or PayPal are restricted by utilizing crypto-to-stablecoin conversion.
• A $4/month DigitalOcean VPS is sufficient for hosting a production-grade monitoring monolith when architecture is kept simple.

Working Examples

Simple GET request used to ping the QuietPulse endpoint after a cron job finishes successfully.

curl "https://quietpulse.xyz/ping/AbCdEf123..."

Practical Applications

• Use Case: SaaS background task monitoring where a job must run every 5 minutes. Pitfall: Relying on complex dashboards instead of simple heartbeat alerts, leading to delayed response times.
• Use Case: International payment processing using NOWPayments for services in regions without banking infrastructure. Pitfall: Higher user friction during the checkout process compared to traditional fiat payments.
• Use Case: Self-monitoring maintenance tasks within the QuietPulse system. Pitfall: Failing to monitor the monitoring service itself, creating a single point of failure.

References:

• https://dev.to/quietpulse-social/how-we-built-a-cron-job-monitoring-system-that-actually-works-1ha4
• https://quietpulse.xyz/blog