Know before your customers do.
Pulsy watches your websites and APIs around the clock. It tracks uptime, response time, and TLS expiry, groups failures into incidents, and alerts you the moment something breaks. Self-hosted and open-source — your monitoring data stays yours.
AGPL-3.0 · Free forever · Runs on your own infrastructure
Every minute of downtime costs you.
Downtime quietly drains revenue, breaks customer trust, and triggers SLA penalties — and most teams find out last, from a customer complaint instead of an alert.
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're issuing credits and writing apologies instead of fixing the incident.
How Pulsy works
From your first check to a public status page in minutes.
- 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.
- 02
Pulsy checks, around the clock
On every interval Pulsy runs the check, records the response time, and watches your TLS certificate expiry.
- 03
Detect & group incidents
When checks fail past your threshold, Pulsy marks the monitor down or degraded and opens a single, clean incident.
- 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.
Monitor sharing
Select monitors and send an expiring link — recipients add the configurations to their own account in one click.
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.
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.
Every feature, always on
When you self-host, the full open-source feature set is on by default, with unlimited monitors — no tiers to unlock.
Encrypted secrets
Email-provider credentials are encrypted at rest with AES-256-GCM.
Rather not run it yourself? We'll host it.
Pulsy Cloud is the same open-source Pulsy, fully managed and operated for you — no servers to set up, patch, or babysit. Sign up and start monitoring in seconds.
Self-hosted Pulsy is free forever — Cloud is simply for teams who'd rather not run the infrastructure. See the self-hosted option
Free
Everything you need to keep an eye on a handful of endpoints.
- 10 monitors
- Checks as frequent as every 5 min
- 30 days of history
- 1 status pages
- Default-domain status pages
- Single seat
- No public API
- No SLA reports
- Priority support
Pro
More monitors, tighter check intervals, longer history.
Billed yearly at $120
- 50 monitors
- Checks as frequent as every 30s
- 390 days of history
- 5 status pages
- Custom-domain status pages
- Single seat
- Limited API access
- No SLA reports
- Priority support
Team
Multi-seat, SLA reports, full API, custom-domain status pages.
Billed yearly at $390
- 200 monitors
- Checks as frequent as every 30s
- 730 days of history
- 25 status pages
- Custom-domain status pages
- 10 seats
- Full API access
- Monthly SLA reports
- Priority support
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.
$5,600per minute
The average cost of IT downtime
Source: Gartner
Self-hosted Pulsy vs. hosted monitoring services
Run Pulsy yourself for free, or let us host it — either way it's the same open-source code, and never a proprietary black box.
| Feature | Pulsy (self-hosted) | Pulsy Cloud | Typical hosted SaaS |
|---|---|---|---|
| Cost | Free forever — unlimited monitors | Free tier, paid plans from $12/mo | Monthly subscription, limits per plan |
| Data ownership | Stays on your infrastructure | Hosted by us, exportable, never sold | Stored on the vendor's servers |
| Open source | Yes — AGPL-3.0 | Yes — runs the same AGPL-3.0 code | Proprietary |
| Customization | Full source access | Full source access — self-host any time | Limited to vendor features |
| Notification channels | Email, webhook, Slack, Discord, Telegram | Email, webhook, Slack, Discord, Telegram | Often limited to higher tiers |
| Public status pages | Included | Included — custom domains on paid plans | Often a paid add-on |
| Vendor lock-in | None | None — export and self-host any time | Migration is costly |
Frequently asked questions
Everything you need to know before you deploy.
What is uptime monitoring?
Is Pulsy really free?
Is the open-source version still free?
What can Pulsy monitor?
How does Pulsy notify me?
Can I share a public status page?
What do I need to run Pulsy?
How is my data protected?
Does Pulsy support multiple languages?
What's the difference between self-hosted Pulsy and Pulsy Cloud?
What does Pulsy Cloud add?
Start monitoring in minutes.
Deploy Pulsy on your own infrastructure and never be the last to know about an outage again.