Introducing siteRabbit

We've spent years on-call for production systems. The tooling options were always the same: pay enterprise prices for something that does 80% of what you need, or cobble together open-source scripts that break whenever a dependency changes.

siteRabbit started as an internal tool. We wanted real multi-region checks (not a single point of failure), signed webhooks we could wire into our own tooling, and status pages that didn't look like they were built in 2008. Most importantly, we wanted it to be fast to set up — under five minutes from signup to first alert.

What we built

13 monitor types. HTTP/HTTPS, SSL, DNS, domain expiry, TCP, ping, heartbeats, sitemaps, broken links, Lighthouse scores, app health endpoints, UDP, and gRPC. Every layer of your stack in one place.

9 notification channels. Email, Slack, Discord, Microsoft Teams, PagerDuty, SMS, webhooks, Telegram, and OpsGenie. With per-channel event filtering so Slack gets the warning and PagerDuty gets the outage.

Beautiful status pages. Custom domains, subscriber email notifications, incident timelines, RSS feeds, and embeddable badges. Everything your users need to trust your service.

A real API. Scoped keys, rate-limited endpoints, signed webhook deliveries with retry and delivery logs. Built for automation.

Pricing that makes sense

We're launching with five plans from $17/month, all starting with a 12-day free trial — no credit card required. Every plan includes all monitor types, all notification channels, 90-day uptime history, and public status pages.

The only difference between plans is how many monitors you can run. We think that's the right axis.

What's next

We're just getting started. On the roadmap:

• SAML/OIDC SSO for enterprise teams
• More monitor types (gRPC health, database reachability)
• On-call schedules and escalation policies
• Scheduled reporting and weekly digests

Start your free trial — it takes less than a minute.