StatusPulse

Uptime Monitoring

Uptime Monitoring and Public Status Pages

Uptime monitoring and status pages, without the enterprise price.

Be the first to review
byMarcelo JarrettaVerified builder

Launched November 2, 2026· Week 36

About

StatusPulse combines uptime monitoring and public status pages in a single product, at a fraction of what a separate status page and monitoring tool cost together. It checks websites, APIs, servers, ports, SSL certificates, DNS records and domain expiry, and goes deeper than most monitors: Postgres, MySQL, SQL Server and Redis databases, gRPC Health, WebSocket and email round-trips — 11 probe types in all. When something breaks, your team hears about it by email, SMS, Slack, Teams or webhook, and your users see it on a branded status page with a custom domain. Incident timelines, post-mortems, AI-drafted updates, on-call escalation and scheduled PDF reports are built in. Free plan available; paid plans from $5/mo. Customer data stays in the EU.

From the founder

Marcelo Jarretta

Who is StatusPulse for?

SaaS companies with 5-50 engineers, usually Series A-B, whose customers open a status page when something breaks. Most of them pay $150-300 a month today for Atlassian Statuspage plus a separate uptime monitor such as Pingdom or Better Stack. It also fits solo founders who want a proper status page for their first paying product without a second bill, and European teams who want their monitoring data kept in the EU.

What problem does StatusPulse solve?

Teams have usually needed two tools and two bills. An uptime monitor tells you something is down; a separate status page is where you tell customers, by hand, often after the support tickets have started. Most monitors also only check that a URL returns 200, so a dead database, a broken gRPC service or a mail server that accepts mail but never delivers it still shows green. Teams worked around this with custom health endpoints, cron scripts and self-hosted Uptime Kuma, or found out from their customers. StatusPulse does it in one place: it runs the checks, proposes an incident when a probe keeps failing, drafts the customer update with AI, and updates the status page, subscribers, on-call, Slack and Teams.

How is StatusPulse different from the alternatives?

Atlassian Statuspage charges $99/mo for its Startup plan and includes no monitoring; StatusPulse Pro is $19/mo with monitoring, a custom domain and branding. UptimeRobot and Pingdom mostly check HTTP, ping and ports; StatusPulse has 11 probe types, including real Postgres, MySQL, SQL Server and Redis checks, gRPC Health, WebSocket and an end-to-end email round-trip. Better Stack prices per responder plus add-ons; StatusPulse charges one flat price per plan. Uptime Kuma is free but self-hosted and goes down with your own infrastructure; StatusPulse checks from outside, with nothing to patch. Data is hosted in the EU, paid plans get their migration done for them within one business day, and the founder answers every support email.

How much does StatusPulse cost?

Free forever, with no card and no trial clock: 10 probes, 3 status pages, 5-minute checks and email alerts. Paid plans are monthly subscriptions, or annual at 10 times the monthly price (two months free). Starter is $5/mo: 20 probes, 5 status pages, 2-minute checks. Pro is $19/mo: 100 probes, 10 status pages, 1-minute checks, custom domain, branding, on-call and AI-drafted incident updates. Business is $49/mo: 500 probes, 25 status pages, 30-second checks, checks from the US as well as the EU, database probes and SSO. Every paid plan has a 14-day money-back guarantee on the first payment, and you can cancel any time and drop to Free at the end of the period.

What's next for StatusPulse?

An AI root-cause copilot that reads the probe timeline during an incident and suggests the likely cause before you write the first update. SAML single sign-on, alongside today's OpenID Connect SSO. More on-call paging channels, Slack and voice calls, on top of email and SMS. And a self-serve importer for UptimeRobot, Pingdom and Atlassian Statuspage, so switching no longer needs an email to support.

Startup Battle record

StatusPulse went 9–7 (56% wins) in the Startup Battle in week 35, where visitors pick the better of two startups head to head. It faced 14 different startups.

and 2 more opponents

Reviews

Comments

Sign in to leave a comment

Sign In