StatusCake is a closed-source hosted uptime and page-speed monitor that spreads features across tiers. 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.
- Open source (AGPL-3.0) — self-host free forever with every capability on.
- 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.
- Cloud plans have published prices and limits; hosting and maintenance are included.
- 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.
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 | StatusCake |
|---|---|---|---|
| Pricing | Free forever — you run it (AGPL-3.0) | Free tier, paid plans from $12/mo | Free tier + paid 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 StatusCake |
| Feature gating | Every capability on, no tiers | Cloud limits vary by plan; WhatsApp and SLA reports require Team | Features vary 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 | StatusCake Pages has separate plans |
| Notification channels | Email, webhook, Slack, Discord, Telegram and optional WhatsApp gateway | Email, webhook, Slack, Discord and Telegram; WhatsApp on Team | By tier |
| Dashboard | Localized (5 languages, RTL) | Localized (5 languages, RTL) | Check the vendor’s current language support |
Native JSON import/export transfers supported monitor configuration, not a full account backup. History, private request values, heartbeat tokens, publication settings and recipient addresses are excluded. Re-enter secrets and check destination compatibility before importing.
Yes. Pulsy is open source under AGPL-3.0-or-later — uptime, TLS-expiry, incident tracking, notifications, and status pages, free forever when you self-host, or managed on Pulsy Cloud from $12/mo.
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.
Yes. Pulsy tracks TLS certificate expiry on HTTPS monitors and can alert via email, webhook, Slack, Discord, or Telegram.
Pulsy records response time on every check and charts it over time, but it does not run full page-speed audits. If synthetic page-speed scoring is what you need, StatusCake covers more there.
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.