Know the moment something goes down

Frequently asked questions

How does pricing work? Is there a free tier?

EvoHub is usage-based, not per-seat. You get free EvoHub tokens every month with no credit card required. Uptime checks are billed per check at a tiny rate, so a team of 50 engineers pays exactly the same as a team of 5 for identical usage.

How frequently can checks run?

The minimum check interval is 30 seconds. You can configure intervals from 30 seconds up to 24 hours depending on how tightly you want to monitor a given endpoint.

Which alert channels are supported?

Uptime alerts can reach your team via email, voice call, and mobile push notification, with SMS coming soon. Alerts also integrate directly with EvoHub On-Call to page the right person on your schedule.

Where do checks run from?

Checks run from EvoHub's infrastructure, outside your own network, so an outage is confirmed from the outside before anyone gets paged.

What monitoring integrations are supported?

Uptime monitors support HTTP and HTTPS, ICMP ping, TCP port, and keyword presence or absence in the response body. HTTP monitors can also track SSL certificate expiry. Every check records the HTTP status code and response time so you can spot problems early.

Can you monitor cron jobs and background workers?

Yes, with heartbeat monitors. Instead of us probing an endpoint, your scheduled job pings a unique URL each time it runs, and EvoHub alerts you the moment a ping is overdue — a dead-man's switch for cron jobs, nightly backups, and workers that have no public endpoint. You set the expected interval (from minutes to daily or weekly) and a grace period, and overdue heartbeats route into On-Call like any other incident.

How does On-Call tie into Uptime?

EvoHub Uptime and EvoHub On-Call share the same platform. When a monitor fires, you can route the incident directly into your On-Call escalation policy so the right engineer gets paged via voice or push (SMS coming soon) without any extra configuration.