Skip to content
Sign inStart free

Use case

Create a public status page from selected monitors and explicitly publish the information you want to share. Cloud Free includes one page on the default domain. Custom domains require Cloud Pro or Team, or a self-hosted deployment with domain routing configured.

Start monitoring free
status.example.comDEMO DATA
Partial outage
Marketing siteOperational
Public APIOperational
Checkout serviceDown
09:11 · Published update

We’re investigating checkout errors. Website and API remain available.

The problem

  • Status-page SaaS products bill separately from monitoring and add their own branding.
  • Teams want status on their own domain, not a vendor subdomain.
  • Keeping a status page in sync with actual monitoring usually means wiring two tools together.

How Pulsy helps

  • Status pages are built in — the same monitors you check power the public page automatically.
  • Custom domains are available on Cloud Pro/Team and configured self-hosted deployments; Cloud Free uses the default domain.
  • Measured health appears after checks complete. Optional history and announcements require explicit public disclosure or publication.
  • One managed tool covers both the monitoring and the status page, so they never drift apart.

  1. Example: create a draft page, select the public components and review their public names. Preview disclosures before publishing.
  2. Choose the interval, timeout and failure threshold. For HTTP checks, configure the expected status and any body, header or JSON assertions.
  3. Configure a notification channel, send an explicit test, and review the first recorded result.

Detection depends on the check schedule, timeout and failure threshold. Delivery depends on your channel provider; alerts are not instantaneous.

Example setup

Illustrative inputs and responses — not a live check or an import file.

Checkout API
Website
Background jobs

Example public display names. Select only the intended monitors, review the preview and publish explicitly. Free Cloud pages use the default domain; custom domains require an eligible paid plan.

Create a public status page from selected monitors and explicitly publish the information you want to share. Cloud Free includes one page on the default domain. Custom domains require Cloud Pro or Team, or a self-hosted deployment with domain routing configured.

Uses the latest recorded observations; failed or stale observations are shown honestly. Announcements and optional history are published separately.

Public status pages are supported. Cloud Free includes one page on the default domain; Pro includes five and Team 25, with custom domains on Pro/Team. Self-hosted deployments support custom domains.

Track Linux host CPU, RAM, swap, filesystem use, load and uptime alongside website checks. Sustained resource pressure and a disconnected agent become actionable incidents.

Create a server monitor, then run its one-command systemd installer or Docker Compose setup. The agent reports over outbound HTTPS; Linux amd64 and arm64 are supported.

Default thresholds are 90% for CPU, RAM and each filesystem: 3 violating reports to alert, 2 healthy reports to recover. Missing reports cause an outage after 3 intervals. RAM alerts are not confirmed OOM events.

Available on every Cloud plan. Each server uses one monitor slot. Reports default to 60 seconds, subject to the plan’s minimum interval; history follows plan retention.

Explore Linux server monitoring

Start with one website or Linux server. Understand the incident and know what to tell your customers.

Start monitoring freeSelf-host on GitHub