What is Statsy and what does it do?

Statsy is a hosted status page service for developers and small teams. It combines three things in one product: a public status page your users can check, automated uptime monitoring that detects when a service goes down, and incident updates that keep subscribers informed. You can start on a free plan without a credit card, and the site states an average setup time of about five minutes from signup to a live page.

It fits teams that want a transparent "here's what's working right now" page without building or maintaining one themselves. It is not a full incident management or on-call platform — the scope is the status page, the monitoring behind it, and the notifications that go out.

What you get

Public status page

The core deliverable is a page at your own domain. On paid plans this is a custom domain such as status.yoursite.com. The page shows:

• A per-service status for each component: Operational, Degraded, or Outage
• A 90-day uptime history, tracked automatically
• A one-click email subscribe for visitors — no account required on their side

The demo on the site shows a typical layout: a list of services (Website, API, Auth, Database, Email Delivery, Dashboard), each with a status dot, plus a headline uptime figure like "90-day uptime — 99.4% · 13 days without incident."

Uptime monitoring

Statsy checks your endpoints on a schedule and updates the status page automatically when something changes. The site lists a 1-minute monitoring check interval on Pro. Monitored endpoints can include things like an API health route (https://api.yourapp.com/health), a marketing site, or a dashboard — each with its own response time and status.

Incident updates and alerts

When a check fails, Statsy changes the status and fires alerts. The example flow on the site: a dashboard endpoint times out, the status flips to Outage, an email goes out from [email protected] saying the page has been updated automatically, and a follow-up "Recovered" email goes out when the endpoint comes back. Past incidents are logged on the page with a resolution note — for example, "Elevated response times on /v1 endpoints. Resolved after scaling connection limits."

Scheduled maintenance

You can post planned maintenance windows in advance, with a time range and a list of affected services. The example on the site shows a database migration window with "Affected: Website, API" and a note that delays may occur.

How the pieces fit together

The practical effect: when something breaks, your users find out from the page and from an email rather than from a support ticket or a tweet.

Who it's for

• Small teams without a dedicated status page. The pitch is "no onboarding calls, no complexity" — you sign up, add endpoints, and the page is live.
• Developers who want monitoring and a status page in one place. Instead of wiring an uptime checker to a separate hosted page, both live in the same product.
• Teams that want to start free and upgrade later. The site frames it as "Start free. Grow when ready," with custom domains and the 1-minute check interval on paid plans.

What to check before committing

• Custom domain is a paid feature. If status.yoursite.com matters to you, plan for a paid plan.
• Check interval differs by plan. The 1-minute interval is listed for Pro; the free plan's interval isn't stated in the material here, so confirm it if fast detection matters.
• Pricing details aren't in the source. The site says "$0 to get started on free plan, forever" but doesn't list paid tiers here — check the pricing page for current numbers.
• Scope. This is status pages and monitoring, not a paging/on-call system. If you need escalation policies or phone alerts, that's a different tool.

The fastest way to judge it is to try the demo or a live example linked from the site, then decide whether the free plan's limits cover your services.