Pulsy
Open-source · Self-hosted

Know before your customers do.

Pulsy watches your websites and APIs around the clock — tracking uptime, response time, and TLS expiry, grouping failures into incidents, and alerting you the moment something breaks. Self-hosted and open-source, so your monitoring data stays yours.

Get startedView on GitHub

AGPL-3.0 · Free forever · Runs on your own infrastructure

Monitors
All systems operational
Marketing site
99.99% uptime
Public API
99.95% uptime
Checkout service
99.40% uptime
Docs
100.0% uptime

Every minute of downtime costs you.

Downtime quietly drains revenue, breaks customer trust, and triggers SLA penalties — and most teams find out last, when a customer complains instead of a monitor.

Lost revenue

Every minute your checkout, API, or app is unreachable is revenue you never get back — and conversions you can't recover.

Finding out from customers

Nothing erodes trust faster than a customer reporting your outage on social media before you even knew it was down.

Silent TLS expiry

An expired certificate takes your entire site offline in one moment — and it always seems to happen over a weekend.

SLA breaches

Miss your uptime commitment and you are handling credits and apologies instead of fixing the incident.

How Pulsy works

From your first check to a public status page in minutes.

  1. 01

    Add a monitor

    Point Pulsy at any URL and choose a check interval, method (GET, HEAD, or POST), and the status code you expect.

  2. 02

    Pulsy checks, around the clock

    On every interval Pulsy runs the check, records the response time, and watches your TLS certificate expiry.

  3. 03

    Detect & group incidents

    When checks fail past your threshold, Pulsy marks the monitor down or degraded and opens a single, clean incident.

  4. 04

    Alert & keep customers informed

    Pulsy notifies your channels instantly and updates your public status page automatically — no manual posting.

Everything you need to stay online

A complete monitoring toolkit — no add-ons, no upsells, every feature always on.

GET, HEAD & POST checks

Monitor websites and APIs with configurable methods, timeouts, and expected status codes.

TLS certificate watch

Get warned before certificates expire so you never get caught by a silent HTTPS outage again.

Incident grouping

Repeated failures collapse into one incident with a clear start, end, and total duration.

Multi-channel alerts

Email, webhook, Slack, Discord, and Telegram — notify the right people, on the channel they actually watch.

Public status pages

Share a clean, branded status page so customers always know what's happening — no login required.

Response-time & uptime history

Track uptime percentage and response-time trends over time with clear, readable charts.

Your monitoring. Your data. Your infrastructure.

Pulsy is open-source under AGPL-3.0 and runs entirely on your own servers. Your monitors, alerts, and status data stay under your control.

Deploy PulsyRead the docs

100% self-hosted

Runs in Docker on your own infrastructure — your data never leaves your servers.

Open-source (AGPL-3.0)

Read the code, audit it, extend it, and trust exactly what it does.

All capabilities included

Every capability is always on, with unlimited monitors.

Encrypted secrets

Email-provider credentials are encrypted at rest with AES-256-GCM.

Built in the open

Pulsy is developed transparently on GitHub. Read the source, open an issue, or send a pull request — the project is yours as much as ours.

Star Pulsy on GitHub

$5,600+per minute

The average cost of IT downtime

Source: Gartner

AGPL-3.0 licensed
Unlimited monitors
5 notification channels
5 languages, full RTL

Self-hosted Pulsy vs. hosted monitoring services

The same monitoring while your data stays on your infrastructure.

Self-hosted Pulsy vs. hosted monitoring services
FeaturePulsy (self-hosted)Typical hosted SaaS
Included capabilitiesUnlimited self-hosted monitorsManaged by an external service
Data ownershipStays on your infrastructureStored on the vendor's servers
Open sourceYes — AGPL-3.0Proprietary
CustomizationFull source accessLimited to vendor features
Notification channelsEmail, webhook, Slack, Discord, TelegramMay vary by service
Public status pagesIncludedMay vary by service
Vendor lock-inNoneMigration is costly

Frequently asked questions

Everything you need to know before you deploy.

What is uptime monitoring?
Uptime monitoring is the practice of automatically checking whether your websites and APIs are reachable and responding correctly. A monitor sends requests on a schedule, records the response and timing, and alerts you when something fails — so you can fix issues before they affect customers.
Is Pulsy really free?
Yes. Pulsy is open-source under AGPL-3.0. You self-host it and every capability is always on.
What can Pulsy monitor?
Any HTTP or HTTPS endpoint — websites, APIs, and services — using GET, HEAD, or POST requests with configurable intervals, timeouts, and expected status codes. Pulsy also tracks TLS certificate expiry for HTTPS URLs.
How does Pulsy notify me?
Pulsy sends alerts to email, webhooks, Slack, Discord, and Telegram. You choose which channels fire on downtime, recovery, and TLS expiry — per monitor.
Can I share a public status page?
Yes. Pulsy generates a public status page showing your monitors' current status, uptime, and recent incidents — with no login required for visitors.
What do I need to run Pulsy?
A server with Docker. Pulsy ships with Docker Compose for PostgreSQL, the API server, and the web app — bring up the stack and you're monitoring in minutes.
How is my data protected?
Your monitoring data never leaves your infrastructure. Email-provider credentials are encrypted at rest with AES-256-GCM, and accounts are protected by secure session-based authentication.
Does Pulsy support multiple languages?
Yes — Pulsy is fully translated into English, Arabic, French, German, and Spanish, with complete right-to-left (RTL) support for Arabic.

Start monitoring in minutes.

Deploy Pulsy on your own infrastructure and never be the last to know about an outage again.

Get startedView on GitHub