Feature notebook

What users can do with Uptime Pulse.

Use this page as a product overview and a quick capability guide for operators inside the app. Uptime Pulse is built around organization-owned monitors, clear incidents, focused notifications, and public status sharing.

Monitoring checks

Track HTTP endpoints with clear derived states.

Create GET or HEAD monitors, set intervals, timeouts, and expected status codes. The latest check drives the current state without storing a separate monitor status column.

SSL certificates

Catch expiring certificates before users do.

Enable optional SSL certificate checks for HTTPS monitors. Expired, invalid, or soon-expiring certificates mark the monitor down and trigger the normal incident workflow.

Incidents

Open and close incidents from real transitions.

A down transition opens an incident. A recovery transition resolves it. Degraded checks stay visible without creating false downtime incidents.

Notifications

Notify the organization by email or Slack.

Each user controls email and Slack settings. Down alerts are throttled to reduce flapping noise, while recovery notifications always send.

AI analysis

Get daily analysis only when useful data exists.

Gemma-powered analysis runs for active monitors with recent incidents or anomalies, then stores structured insights for operators to review.

Operator dashboard

Pin the monitors that matter to each user.

The dashboard summarizes pinned monitors, current states, recent incidents, AI insights, and 30 day uptime for the signed-in user.

Public status pages

Publish selected monitors without exposing the rest.

Organizations get unauthenticated status pages for public monitors, active public incidents, 30 day history bars, and cache-friendly SVG badges.

Retention

Keep the right history for the right job.

Checks are pruned after 90 days for storage control. Incidents and AI insights are retained indefinitely so long-range uptime and context remain accurate.

Access model

Invite-only teams with organization scoping.

Platform admins manage organizations and users. Organization members work only with their own monitors, incidents, insights, settings, and public status surface.

Typical workflow

From monitor setup to public communication.

  1. 1 Add organization monitors and choose which are public.
  2. 2 Turn on SSL certificate checks for HTTPS endpoints that need expiry protection.
  3. 3 Let the monitoring queue perform checks and derive state.
  4. 4 Use incidents and notifications to coordinate response.
  5. 5 Review AI insights for patterns after meaningful events.
  6. 6 Share the public status page or embed a monitor badge.

Want to operate from the inside?

Uptime Pulse is still invite-only. Send a short application and describe what your team needs to keep online.

Request an invite