UptimeRobot is a solid hosted monitor, but its plans scale by paid monitor count, features unlock by tier, and the code is closed. Pulsy runs the same HTTP, keyword, and TLS-expiry checks and is open source under AGPL-3.0 — self-host it free forever on your own infrastructure, or run Pulsy Cloud on flat plans that are never billed per monitor.
- Open source (AGPL-3.0) — read the code, fork it, or self-host it free forever with every capability on.
- No per-monitor billing. Self-hosted has no bill at all; Pulsy Cloud is flat plans.
- Cloud Free, Pro and Team have different capacities and API, channel and reporting access. WhatsApp and SLA reports require Team. Pro API access is read-only; Team supports reads and writes. Self-hosting includes the full feature set.
- Localized dashboard in five languages with full right-to-left support.
Pulsy supports HTTP, DNS, TCP and interval-based job heartbeats. Cloud capacities and API, channel, reporting and domain access depend on the plan. Self-hosting has no subscription cap on monitors or status pages; practical capacity depends on server resources, workload and retention. Check the destination release for supported features before migrating.
On narrow screens, scroll the table sideways to compare all columns. Keyboard: focus the table region and use the arrow keys.
| Feature | Pulsy (self-hosted) | Pulsy Cloud | UptimeRobot |
|---|---|---|---|
| Pricing | Free forever — you run it (AGPL-3.0) | Free tier, paid plans from $12/mo | Free tier + paid per-monitor plans |
| Source code | Open source, AGPL-3.0 | Managed Pulsy service; verify release compatibility before migrating | Proprietary |
| Where your data lives | Your own infrastructure | Hosted by Pulsy; configuration-only JSON export (not a full backup) | Hosted by UptimeRobot |
| Pricing model | No software subscription; capacity depends on your infrastructure | Flat plans, not per-monitor | Priced by monitor count |
| Feature gating | Every capability on, no tiers | Cloud limits vary by plan; WhatsApp and SLA reports require Team | Integrations and features by tier |
| TLS expiry monitoring | Built in | Built in, every plan | Built in |
| Status pages | Included, custom domains | Free: 1 default-domain page; Pro: 5 and Team: 25, with custom domains | Free includes one basic page; paid plans add capacity and customization |
| Dashboard | Localized (5 languages, RTL) | Localized (5 languages, RTL) | Check the vendor’s current language support |
Re-create the supported checks and notification settings in Pulsy, then run both monitors while you verify the results. Native Pulsy JSON import/export covers supported configuration only; it does not import competitor exports or transfer history, secrets, recipients or publication settings. Check the destination release before moving between Cloud and self-hosting.
Yes. Pulsy is open source under AGPL-3.0-or-later. Self-host it free forever with every capability on and no monitor limit, or use Pulsy Cloud (free tier, paid plans from $12/mo) if you would rather not run it yourself.
Cloud plans include 10, 50 or 200 monitors at fixed plan prices. More capacity requires a higher plan; there is no per-check charge. Self-hosting requires your own infrastructure.
Yes. Pulsy watches TLS certificate expiry on every HTTPS monitor and can alert you before a certificate lapses, alongside up/down and degraded status.
Public status pages are supported. Cloud Free includes one page on the default domain; Pro includes five and Team 25, with custom domains on Pro/Team. Self-hosted deployments support custom domains.
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 monitoringStart with one website or Linux server. Understand the incident and know what to tell your customers.