Drumbeats

Yes, the Free plan is $0 forever with no credit card required. It includes 50 monitors, 200,000 Beats per month, unlimited team seats, and every notification channel. The limits are: 100 KB max payload size, 250 ping-history entries per monitor, status pages keep Drumbeats branding, and minimum interval is 1 minute (Pro drops it to 30 seconds). For most teams running a few dozen background jobs, Free is genuinely all they need.

No. Drumbeats is a single HTTP request with no SDK, no daemon, and no library to vendor in. Your job sends a curl or any equivalent HTTP call to its monitor URL when it succeeds, fails, or starts. The integration is one line of bash for cron jobs, two lines of Python or Node for queue workers. Any environment that can make an outbound HTTPS request can ping Drumbeats.

For FAILED pings or non-zero exit codes, the alert is dispatched within seconds, typically well under 30 seconds end-to-end including delivery to Slack, Email, or your webhook. For MISSED runs (a job that didn't ping), Drumbeats waits for the schedule plus grace period to elapse before firing, which is configurable per monitor with a default 5 minutes grace. You can also enable failure_tolerance and schedule_tolerance to absorb a single transient hiccup before paging your team.

Yes. Because Drumbeats is ping-based, your job only needs to make an outbound HTTPS call. There is no inbound probing, no allowlist to manage, and no static IPs you need to grant access to. As long as your job can reach the public internet, it can be monitored, even if the rest of your infrastructure is fully private.

Yes. Monitors themselves never consume Beats. You only pay for job executions (pings). You can create as many monitors as your plan allows.