Core concepts

A few terms show up throughout Pulse. Here's the mental model.

Organization (tenant)

Your account is an organization. It owns everything — monitors, pages, incidents, team members and billing. Pulse is path-based multi-tenant: your organization is reached at a path under the Pulse host, using the address (slug) you chose at sign-up:

pulse.servilo.in/acme                 → your console & status page
pulse.servilo.in/acme/manage          → the admin console

There are no per-tenant subdomains to configure — a new organization is just a new path.

Important

Some names are reserved (for example docs, login, platform, api, status) and can't be used as an organization address, because they map to real application routes.

Monitor

A monitor is a single check — an HTTP endpoint, a TCP port, a DNS record, a certificate, and so on. Each monitor has a status (UP, DEGRADED, DOWN, MAINTENANCE, or NO_DATA), a check interval and a region. See Monitors overview.

Workspace

A workspace is an isolated space within your organization for a set of status pages and monitors — useful to separate environments (e.g. production vs staging) or brands. Your public URLs include the workspace:

pulse.servilo.in/acme/production/home

Page

A page is a public status page inside a workspace. A workspace can have more than one page (for example a customer-facing page and an internal one).

Product

A product groups related monitors into a labelled section on a status page (for example "Core Platform", "Payments"). Products keep long status pages organized.

Incident & maintenance

An incident is a communication thread about a problem — with a status, an impact level and timestamped updates.
A maintenance window announces planned work ahead of time and marks affected monitors as MAINTENANCE during the window.

Subscriber

A subscriber is someone who opted in to be notified (by email) when your status changes or an incident is posted.