Skip to content

The product

The full operating surface, in one product.

Telemetry, diagnosis, routing, and forensic history — engineered as one cohesive surface for teams that run their own Linux infrastructure. No agents to glue together. No dashboards to assemble.

Telemetry

Continuous host telemetry

Every signal a Linux operator actually reaches for, captured at second-level resolution.

The agent reports the operational primitives that determine whether a host is healthy: CPU pressure, memory behaviour, disk saturation, load, and the runtime of the services that sit on top. No proprietary formats, no opinion-laden abstractions — just a clean picture of what’s happening on the box.

CPU pressure

Per-core utilisation, steal time, and short-burst spike detection scoped per process.

Memory behaviour

Resident, cached, swap, and page-fault rates surfaced alongside the processes responsible.

Disk and I/O

Free space, inode exhaustion, throughput per volume, and latency per device.

Load and saturation

1, 5, and 15-minute load averages contextualised against your historical baseline.

Uptime tracking

Per-host uptime, reboot detection, and a running ledger of unplanned restarts.

Service supervision

Health probes for nginx, Postgres, Redis, Docker daemons, and any systemd unit you point at.

Diagnosis

Diagnosis engine, not a chatbot

When the page fires, you get a written brief on what broke and why — before you’ve finished opening the laptop.

The diagnosis engine reads metrics, system events, recent service restarts, and config changes the moment an alert opens. It writes a short brief in the language an on-call engineer would use: what failed, what likely caused it, and the first three things worth trying. No prompt engineering required.

Cross-signal correlation

Joins metrics, process state, and recent system events into a single causal chain.

Written incident briefs

A two-paragraph engineering summary attached to every incident, in plain prose.

First-step guidance

Three concrete actions to try first, ranked by how likely they are to resolve the incident.

Change correlation

Cross-references recent deploys, package updates, and cron windows that match the failure.

Severity grading

Each incident is graded so the queue stays sortable when several fire at once.

Routing

Alerts that respect on-call

Threshold-based routing that doesn’t spam, with deduplication built in.

Alert rules are scoped per host, per environment, or fleet-wide, and route to whichever channel the responsible team actually reads. Cooldowns, grouping, and severity gating are first-class — not afterthoughts in a YAML file.

Email

Plain-text and HTML alerts with the full incident brief in the body, not a link to it.

Slack

Threaded incident cards with severity, summary, and quick-resolve actions.

Discord

Webhook-based delivery with embedded summaries — useful for community-run ops channels.

HTTP webhooks

Signed JSON payloads for PagerDuty, Opsgenie, custom routing, or your own automation.

Threshold rules

Per-metric thresholds with hysteresis windows so you don’t flap on borderline signals.

Cooldowns and grouping

Related alerts collapse into one incident; cooldown windows prevent re-firing.

Forensics

An auditable record of every incident

Postmortems shouldn’t begin by reconstructing the timeline from Slack scrollback.

Every incident is captured end-to-end: detection, escalation, diagnosis, mitigation, and resolution. Metric history sits alongside it, so you can show the exact graph that justified the page weeks after the fact.

Full event timeline

Every state change, alert delivery, and operator action recorded chronologically.

Recurrence detection

Identifies the hosts and services that keep showing up in postmortems.

Tiered retention

Seven days on Solo, thirty on Growth, ninety on Scale — all with the same fidelity.

Metric replay

Replay CPU, memory, disk, and load alongside the incident timeline at the original resolution.

Agent

A single static binary

One install command. No package manager fights. No daemons you didn’t ask for.

The agent ships as a single Linux binary under fifteen megabytes of resident memory. It works on Debian, Ubuntu, Alpine, RHEL, and anything else that runs systemd or OpenRC. If your VPS has SSH and curl, it’s supported.

curl-pipe install

One command, signed checksum, agent registers and starts streaming inside a minute.

Provider agnostic

Tested on Hetzner, DigitalOcean, Vultr, Linode, OVH, AWS Lightsail, and bare metal.

Container telemetry

Auto-detects Docker and surfaces container-scoped CPU, memory, and restart history.

Negligible footprint

Sub-1% CPU steady-state, ~12MB RSS, no kernel modules, no userspace tracing overhead.

Workspaces

Workspaces sized for the team

Shared visibility for the people responsible. No per-seat invoices for the rest of the org.

Invite the engineers who carry the pager. Group hosts by environment, customer, or service owner. Route alerts so the right person sees them and the wrong person doesn’t.

Member invitations

Email-based invites, role assignment, and revocation from a single screen.

Shared incident view

Everyone on the workspace sees the same incident, the same diagnosis, the same timeline.

Host grouping

Tag and group hosts by environment, customer, or owning team for filtered views.

Ownership-aware routing

Alerts follow ownership tags to the correct channel, automatically.

Trust

Security held to operator standards

Nothing leaves your host that doesn’t need to. Nothing crosses the wire in the clear.

We treat your telemetry the way you’d treat your own production data. The agent uses a scoped token, communicates over TLS 1.3, and never touches application data, secrets, or user content.

TLS 1.3 + AES-256

Encryption in transit and at rest, with rotated server certificates and HSTS.

Scoped agent tokens

Per-host tokens, individually revocable, with no SSH or shell privileges granted to Pulsewise.

Minimal collection

Operational metrics and service health only. No log streaming, no application inspection.

SOC 2 in progress

Type II controls actively under audit; current security overview available on request.

Get started in under a minute.

Install Pulsewise on your servers and see your first reliability score the same day. Free for 14 days, with every feature included.

No credit card · Full access for 14 days · Cancel anytime