See your sites the way your users do.
HTTPS checks every minute, three retries before an alert fires, SSL-expiry warnings at 30, 14, 7, and 1 days, and a public status page on every monitor. Same Beats budget covers your cron jobs and heartbeats — one plan, one dashboard.
How it works
Three steps. Less than a minute.
Add your URL
Paste the URL, pick an interval (1 min on Free, down to 30 sec on Pro), and the status codes you accept.
Drumbeats checks on schedule
Every check records HTTP code, response time, SSL state, and DNS resolution. Failures trigger three retries five seconds apart.
You hear about it before users do
When the failure threshold is hit, an incident opens and alerts route to Slack, Email, Telegram, Discord, browser push, or a webhook.
The actual product
Three views on the same monitor
Real components, virtual data. The only thing fake is the URL.
Dashboard
Response time, SSL, uptime — at a glance
Every uptime monitor shows the last hours of checks, average / P95 / min / max, and the SSL certificate's days-to-expiry. The chart re-renders as new checks land.
Public status page
A status page on every monitor — instant and free
Toggle a setting in the dashboard, get a public URL. Drumbeats hosts the page, ships it in light and dark themes, and updates it in real time.
- Live in 60 seconds — drop the URL in your homepage footer
- Light and dark themes ship together — viewer’s choice
- Custom subdomain on Pro (status.your-company.com via CNAME)
- Included on every plan, Free included — no add-on, no upsell
Your data
Every check, exportable
The dashboard table lists every individual check with HTTP code, response time, region, and error. One click downloads the lot as CSV — no API plumbing, no plan gate.
What this is for (and what it isn’t)
Uptime alone won’t tell you if your product is working
External uptime monitoring is the oldest category in operations tooling, and also the one teams over-rely on. The question "did my homepage return 200?" is a fair question. The harder ones — "did checkout actually complete?", "is my SSL cert about to expire on a backend that never reaches users?", "did last night’s reconciliation job run?" — are increasingly out of scope for the polling-based legacy tools.
Drumbeats handles the standard uptime work — HTTPS GET/HEAD/POST, status-code validation, response-time tracking, SSL expiry, retry-before-alert (three retries, five seconds apart) — and treats it as one half of a two-part picture. The other half is the inside view: the cron job that should have run, the queue worker that should have consumed, the heartbeat that should have arrived. Most outages live in the gap between the two.
Pricing reflects that. Most uptime SaaS prices per monitor, which discourages the right thing — adding more checks. Drumbeats prices per check, so adding a 51st monitor at any interval costs the same as the first. The Free tier’s 200,000-Beats budget covers a real production setup; Pro at $20/mo covers a heavier one. Neither plan asks you to pick a separate vendor for cron, heartbeat, or status-page coverage.
Slow degradation that never crosses a hard threshold
Response time drifts from 200ms to 800ms over a week. No 5xx, no SSL alarm — but every customer notices. The chart trend surfaces the drift before it becomes a complaint, and `max_duration_seconds` lets you turn it into an incident.
SSL expiry that nobody scheduled a reminder for
A renewal cron broke six weeks ago, nobody noticed, and the cert expires in three days. Drumbeats fires four warnings as the cert crosses 30, 14, 7, and 1 days remaining — a missed renewal cannot slip through silently.
HTTP 200 from a backend that’s actually broken
The homepage is up, but the queue is paused and nightly invoices haven’t run. Pair an uptime monitor with a heartbeat from inside the job that produces the data — silent jobs page you, just like silent endpoints.
Pair an uptime monitor with a heartbeat on the cron that produces the data the page serves. That’s the complete picture: the customer-facing surface, and the backend pipeline that keeps it working.
One ping. You're done.
No SDK, no agent, no library. A single HTTP request is all it takes.
# Create an uptime monitor via the API
curl -X POST https://api.drumbeats.io/v1/monitors \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"project_id": "YOUR_PROJECT_ID",
"name": "My Website",
"type": "UPTIME_HTTP",
"schedule": "5m",
"uptime_url": "https://myapp.com",
"uptime_method": "GET",
"uptime_timeout_ms": 10000
}'What does it cost?
Three honest ways the Free tier holds up
Free includes 200,000 Beats per month, capped at 50 monitors. Each uptime check is 1 Beat. Pick the shape that matches your reality — 22 sites at 5-min checks (~196K Beats), 4 sites at 1-min (~178K), or 50 sites at 15-min (~149K). Mix with cron and heartbeat monitors on the same pool.
Outgrowing Free? Pro at $20/mo gets you 1,000,000 Beats and 30-second intervals. Same plan also covers cron, heartbeat, and queue monitors — no second product to buy.
Drumbeats vs. running a stack of single-purpose tools
UptimeRobot does uptime. Cronitor does cron. StatusPage.io does status pages. Most teams stitch all three together. Drumbeats is the unified version on a single Beats budget — and Free is enough for many of them.
FAQ
Common questions
Your API just returned a 503. Would you know?
Most teams find out from their users. Drumbeats retries three times before alerting, then routes the incident to Slack, Email, Telegram, Discord, browser push, or a webhook within seconds. Not ready to sign up? Try the free one-shot checker first — no account required.
No credit card required · 50 monitors free · Setup in 60 seconds
Keep exploring
What to read next
Related monitoring
- Status pages
Turn any uptime monitor into a customer-facing status page in one click.
- Cron job monitoring
The backend half of the picture — monitor the jobs that keep your APIs healthy.
- Heartbeat monitoring
Use heartbeats for internal services that aren’t publicly reachable.
- Incidents & alerts
Routing, escalation, and acknowledgement workflows for downtime.
Free tools
- Website down checker
One-shot HTTP, DNS, SSL, and TLS check — no account required.
- AI agent setup
Generate a paste-ready prompt that adds uptime monitors via your AI coding agent.
Resources
- Drumbeats vs. Healthchecks.io
How the two heartbeat / uptime tools differ on price and depth.
- Pricing & Beats explainer
See how the Beats budget covers cron, heartbeat, and uptime on one bill.
- Full FAQ
49 deeper technical answers about checks, payloads, and edge cases.