Introduction

Servilo Pulse is a status page and uptime monitoring platform. It continuously checks your services, shows their health on a public status page, and keeps your users informed during incidents and maintenance.

With Pulse you can:

Monitor websites, APIs, TCP ports, DNS records, TLS certificates and domain expiry — or receive heartbeats from your own jobs.
Publish a branded public status page (on a Pulse subdomain or your own custom domain).
Communicate during outages with incidents, and plan ahead with maintenance windows.
Notify subscribers by email and push external alerts into Pulse from your existing tools.
Collaborate with your team using roles and permissions.

How it fits together

Monitors  ──►  collect uptime data every few seconds/minutes
   │
   ▼
Status page  ──►  shows components grouped by product, live status, history
   │
   ├──►  Incidents      (something is wrong — keep users updated)
   ├──►  Maintenance    (planned work — set expectations in advance)
   └──►  Subscribers    (get notified when status changes)

Note

Every account is an organization (also called a tenant). Your organization lives at a path under the Pulse host — for example pulse.servilo.in/acme. See Core concepts for the full model.

Where to go next

New here? Follow the Quick start.
Want to understand the building blocks? Read Core concepts.
Ready to add checks? Jump to Monitors overview.