SolidPing vs Peekaping
Peekaping and SolidPing are close cousins: both are self-hosted, both are written in Go, both exist because Uptime Kuma is excellent right up to the point where it isn't. Peekaping describes itself as "the best Uptime Kuma alternative" for professional DevOps teams, and it is a genuinely nice piece of work — a polished site, a live demo, a community Terraform provider, and pluggable storage.
Both sides here are self-hosted. Peekaping has no hosted service, so the subject of this comparison is SolidPing self-hosted: free, AGPL-3.0, no plan, no caps. We do sell a hosted version and it is described below, but it plays no part in the table.
The differences are about scope. Peekaping is a focused, well-executed uptime monitor. SolidPing is a wider platform: more protocols, checks that run from several places, and on-call built in.
If we've gotten a detail about Peekaping wrong, please open an issue — we want this accurate.
At a glance
| SolidPing (self-hosted) | Peekaping | |
|---|---|---|
| License | AGPL-3.0 | MIT |
| Stars / version | zEr0 (help us grow) | ~1,140 · v0.0.46 |
| Maturity | Production | Self-described beta |
| Cost | Free — unlimited monitors, check rate, workers and status-page domains; 30 members by default | Free — unlimited |
| Stack | Single Go binary, dashboard embedded | Go backend + React frontend |
| Database | SQLite or PostgreSQL | SQLite, PostgreSQL or MongoDB |
| Check types | 40 | ~14 |
| Minimum interval | 10 seconds (browser checks 60 s, JS 30 s) | Configurable |
| Multi-region checks | Distributed workers you run anywhere, lease-based failover | Single instance |
| Private-network probing | Deported agents; the server cannot decrypt their credentials | Runs wherever you install it |
| On-call & escalation | Rotation schedules, overrides, iCal feeds, multi-step escalation | Not available |
| Alert channels | 16, including SMS, voice and WhatsApp through your own Twilio account | 20+ |
| Status pages | Public pages, sections, custom domains, subscribers, Atom feed | Yes |
| Config as code | YAML export / import / apply, REST API, sp CLI | Community Terraform provider |
| AI / MCP | MCP server built in | — |
Where SolidPing is the stronger choice
Protocol coverage. Peekaping covers roughly 14 monitor types — the web and network essentials. SolidPing covers 40, which is the difference between watching your website and watching your whole stack: PostgreSQL, MySQL, Redis, MongoDB, ClickHouse, Oracle; SMTP, IMAP, POP3 and a passive email-reception check; Kafka, RabbitMQ, MQTT, gRPC, SIP; SSH, RDP, FTP, SFTP; SNMP, Docker, Kubernetes; SSL and domain expiry; NTP and DNSBL.
Checks from more than one place. Peekaping runs as a single instance, so it sees your services from one network position. SolidPing runs distributed workers you deploy yourself, with per-region periods and cross-region confirmation, so a blip on one path does not become a page.
On-call. Peekaping alerts; it has no rotation or escalation model. If your team takes turns being woken up, that gap is the whole story.
Private networks without opening one. SolidPing's deported agent connects outbound only and receives age-sealed credentials it decrypts locally — the server never can.
Release cadence, in fairness. Peekaping has been on v0.0.46 since April 2026. That is not a criticism of the code, but if you are choosing something to depend on, the release rhythm is a fact worth knowing.
Where Peekaping is the stronger choice
MongoDB. If your team already runs MongoDB and would rather not add Postgres, Peekaping supports it and SolidPing does not.
More alert channels. 20+ against our 16.
A Terraform provider. There is a community Terraform provider for Peekaping. We offer YAML config-as-code and a CLI, which covers similar ground, but if your infrastructure is already Terraform end to end, that is a real convenience.
MIT rather than AGPL. A simpler licence for anyone who wants to embed or redistribute it.
Smaller surface. If 14 monitor types is all you will ever need, a smaller tool is a smaller thing to operate and understand.
The other model, on both sides
Peekaping has no hosted service — it is a self-hosted product, and running it is part of the deal.
SolidPing has one, and it is the same binary. SolidPing Cloud is free for 100 monitors and 10 checks a minute, then €5 / €15 / €45, checked from six shared regions with nothing for you to deploy. What changes going hosted: plan caps come back on monitors, check rate, seats, agents and status-page domains, and SMS, voice and WhatsApp are not included — those stay a self-hosted capability, since they run on your own Twilio account. If you are comparing two self-hosted tools because you want to self-host, that is a footnote; if you are comparing them because Kuma broke, it may be the shortcut.
Which should you pick?
If you are replacing Uptime Kuma with something in the same shape — one instance, website and network checks, a status page — Peekaping is a reasonable choice and MIT licensing makes it an easy one.
Pick SolidPing when the reason you are leaving Kuma is scope rather than polish: databases and queues to watch, more than one vantage point, or a rotation that needs to page a human.