Are these videos real?

Captured from an isolated local Pulsy deployment with disposable demo data. Timing is shortened for presentation; credentials are omitted. These walkthroughs focus on HTTP monitors and shared workflows; they do not cover every monitor type.

Follow these workflows in your deployment. Cloud availability, capacity and cadence follow your plan; self-hosting has no subscription gates.

Pulsy demos — guided product workflows

Product demos

Eleven short, captioned walkthroughs — everything from your first monitor to public status pages, in your language.

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

CPU pressure on an example host

DEMO DATA

Degraded — sustained CPU pressure

CPUIllustrative reports · CPU threshold 90%

Three consecutive CPU reports at or above 90% activate an incident. Delivery timing depends on your notification channel.

cta.subtitle

cta.primary cta.secondary

See Pulsy in action.

A first lookA guided look at the public site, monitoring workflow and deployment choices.

Create your first monitorConfigure a URL and check policy, then review the first observation.

The dashboard at a glanceHealth summaries, filters, saved views and named More menus.

Response time & uptimeRecorded HTTP timing, daily history and configuration.

Multi-channel alertsEmail, webhook, Slack, Discord, and Telegram — per monitor, per event.

Incidents & check historyMeasured incidents and available check history.

Public status pagesPublish a page your users can check — no login required.

Monitor sharingSend monitor configurations to anyone with an expiring link.

Five languages, full RTLEnglish, Arabic, French, German, and Spanish — with true right-to-left for Arabic.

Dark & light modeOne click to switch, remembered everywhere.

Edit anything, anytimeChange URLs, intervals, and thresholds — applied on the next check.

Watch the server behind your website.

CPU pressure on an example host

cta.title