Server monitoringNow on Windows

Every server,
inside out.

One lightweight agent for Linux, macOS and Windows. CPU, memory, disk and network every 30 seconds, for a fraction of Datadog’s price.

1 server and 20 monitors free. No credit card required.

Trusted by teams that put uptime first.

Read customer stories

Six signals, every 30 seconds. From every host, in one place.

  • cpu 23% · load 0.84 0.91 0.88

    CPU and load average

    User, system and iowait time as a share of wall time, with 1, 5 and 15-minute load averages. On Windows, load comes from the processor queue.

  • memory 61% · 0.7 of 1.2 GB

    Memory

    Used, available and total memory, and utilization as a percentage. A leak shows up as a slope days before it takes the host down.

  • / 39% · /data 57% · C: 63%

    Disk space per mount

    Used and free space for every real mount point, with pseudo-filesystems left out. On Windows, each drive letter is a mount.

  • nvme0n1 · read 12 MB/s · write 3 MB/s

    Disk I/O

    Bytes read and written per block device, to find the drive that saturates when requests start to queue.

  • eth0 · in 4.1 Mb/s · out 0.6 Mb/s

    Network throughput

    Bytes in and out per interface, turned into download and upload rates in the dashboard. Loopback and virtual adapters are left out.

  • ubuntu-22.04 · amd64 · up 41 days

    Host info and uptime

    Hostname, OS, kernel, architecture, CPU model, boot time and agent version, current on every scrape. The dashboard flags agents with an update waiting.

Your checks see the outside. The agent sees the inside.

Servers sit in the same project as your monitors, alert through the same escalation policies and page the same on-call.

  • api.acme.com · 502 · 3 regionsprod-api-01 · memory 97%

    The check fails, the host explains

    An uptime monitor tells you the API stopped answering. The agent on the host behind it shows the memory it ran out of, in the same project.

    Uptime monitoring
  • cron · nightly-backup · misseddb-01 · /data 100% full

    The backup that never ran

    Cron job monitoring catches the job that didn’t check in. The disk space chart of the database host shows why it couldn’t.

    Cron job monitoring
  • worker-03 · silent for 90 soutage opened · on-call paged

    The host that went quiet

    When a server stops reporting, an outage opens and its escalation policy pages whoever is on call, exactly as it does for your monitors.

    On-call scheduling

A server goes quiet. The right person hears about it.

  1. OnlineEvery 30 seconds

    Metrics arrive on every scrape. Liveness comes from them, there is no separate heartbeat.

  2. Stale30 s without data

    Flagged in the dashboard only. A network blip doesn’t wake anyone up.

  3. Offline90 s by default

    An outage opens and the server’s escalation policy pages its channels. The threshold is yours to tune, from 60 seconds.

  4. RecoveredFirst metrics back

    The outage resolves and the same channels get the recovery notification.

Every channel.Wherever your on-call is.

Bind an escalation policy to each server. Its steps, delays and channels apply as they do for your monitors.

  • Slack
  • Microsoft Teams
  • Google Chat
  • PagerDuty
  • Opsgenie
  • Jira Service Management
  • Discord
  • Telegram
  • Mobile app
  • Email
  • SMS
  • Phone call
  • Webhooks

Installed in one line. Linux, macOS or Windows.

  1. 1

    Add a server

    In the dashboard, open Servers and click New server. Hyperping gives you the install command with your project’s token.

  2. 2

    Run one command

    With sudo on Linux and macOS, in an Administrator PowerShell on Windows. The installer checks the download’s SHA256 and registers a service.

  3. 3

    Watch the charts fill in

    About 30 seconds later the server turns Online and its CPU, memory, disk and network charts start to move.

install.shShell
# Linux (systemd) or macOS (launchd), amd64 or arm64, with sudo
curl -fsSL https://hyperping.com/install.sh | sh -s HP_INSTALL_xxxxx

Built to live on production hosts. Small, quiet and hard to break.

  • ~50 MB RSS · 30 s scrape

    Light enough for production

    The agent targets about 50 MB of memory and scrapes every 30 seconds, next to your app rather than on a monitoring box.

  • /var/lib/hyperping/queue

    Metrics survive outages

    Unsent batches wait in a queue on disk and are retried, so graphs stay whole through reboots, network blips and ingest outages.

  • OTLP/HTTP · gzip

    OpenTelemetry inside

    An embedded OpenTelemetry collector reports standard hostmetrics names over OTLP/HTTP. No collector of your own to run.

  • outbound 443 only

    No inbound ports

    The agent only calls out over HTTPS. Nothing listens on the host and nothing needs opening in your firewall.

  • install token → host token

    One credential per host

    The install token is swapped for a token of the host’s own. Re-run the installer to rotate it, or revoke it from the dashboard.

  • --name --policy --group

    Made for fleets

    Set the name, escalation policy and group at install time from Ansible, Terraform or a DaemonSet. Re-installs keep the edits made in the dashboard.

Powering businesses of all sizes.From fintech to global agencies, teams know first.

A fraction of Datadog’s price.Agents come with the plan, next to your monitors and on-call.

USD · Annual billing on both sides

Datadog

Infrastructure monitoring, billed per host.

Infrastructure Pro
  • Host monitoring20 hosts × $15
    $300/mo
  • Uptime checksSynthetic API tests, billed per run
    +$5/10k runs
  • On-callSchedules and paging, billed per seat
    +$20/seat
Host monitoring alone

$300/month

$3,600 over 12 months

Servers, uptime, status pages and on-call.

Pro
  • 20 server agents
  • 250 uptime monitors
  • 3 public or private status pages
  • On-call & escalation policies
  • 14 days of 1-minute history
One plan, every agent included.

$74/month

$890 billed yearly
75% less

Save $2,710 a year on 20 servers, before Datadog’s uptime checks and on-call.

Compare New Relic and Netdata too
Pricing sources & assumptions

Reviewed . All amounts are USD per month on annual billing; local currency prices may differ.

  • Datadog Infrastructure Pro: $15 per host per month billed annually, $18 on demand. Synthetic API tests are $5 per 10,000 runs and On-Call $20 per seat per month on annual billing. APM, logs and custom metrics are billed on top and left out.
  • Hyperping: the smallest plan that includes every agent, at its yearly price divided by 12. Extra agents are $2 a month, $1.50 on Business, so a smaller plan with extra agents can cost less.

Questions about server monitoring.

Which operating systems does the agent support?

Linux with systemd and macOS with launchd, on amd64 and arm64, and Windows 10 or Windows Server 2016 and later on amd64. Linux and macOS use a one-line shell installer, Windows a one-line PowerShell installer that registers a Windows service. See Install the agent for the details.

How much does server monitoring cost?

The Free plan includes 1 server agent with 2 days of metric history. Essentials includes 5 agents, Pro 20 and Business 100, with server alerting on every paid plan. Extra agents are $2 a month, or $1.50 on Business. See pricing, or compare Datadog, New Relic and Netdata host by host in the server monitoring cost calculator.

Will the agent slow my servers down?

The agent targets about 50 MB of memory and scrapes host metrics every 30 seconds. It is built to run on production machines next to your workload, not on a dedicated monitoring host.

What happens when a server goes offline?

A server turns Stale after 30 seconds without metrics, which only shows in the dashboard. Once its offline threshold passes, 90 seconds by default and 60 at the least, an outage opens and the escalation policy bound to the server pages its channels. When metrics come back, the outage resolves and a recovery notification goes out. See Server alerting.

Does the agent need inbound ports or a VPN?

No. The agent only makes outbound HTTPS requests to api.hyperping.io and ingest.hyperping.io. If they fail, metrics are queued on disk and sent once the connection is back.

How long are server metrics kept?

At 1-minute resolution, 2 days on Free, 7 on Essentials, 14 on Pro and 30 on Business. Coarser rollups are kept longer: up to 6 months of hourly points on Essentials and 13 months on Pro and Business. See Metrics collected.

Does it work with containers and Kubernetes?

For host metrics, yes: install the agent on the VM or node, for example with a DaemonSet, and you see that machine’s CPU, memory, disk and network, including the load of the containers it runs. Per-container and per-process metrics are not collected.

How is Hyperping different from Datadog?

Datadog is a full observability platform, with APM, logs and traces billed per host, per gigabyte or per event. Hyperping covers host metrics, uptime monitoring, status pages and on-call in one plan with a fixed price. If you need trace search or log retention, you need an observability tool. Read the Datadog alternative comparison.

Your first server, in a minute.