SolidPing vs Kuvasz
Kuvasz is one of the most under-appreciated projects in self-hosted monitoring. It has been shipping since 2020, it is AGPL-3.0 like us, and it is unusually complete for its size: private status pages, maintenance windows, YAML-declared monitors, Prometheus and OTLP exporters, a Home Assistant integration, and an MCP server since v4.0.0.
Both sides here are self-hosted. Kuvasz has no hosted service, so the subject is SolidPing self-hosted — free, AGPL-3.0, no plan attached. Our hosted version is described below and does not feature in the table.
Kuvasz is also deliberately narrow. It does six things and does them carefully. SolidPing does forty and takes on the complexity that comes with that.
If we've gotten a detail about Kuvasz wrong, please open an issue — we want this accurate.
At a glance
| SolidPing (self-hosted) | Kuvasz | |
|---|---|---|
| License | AGPL-3.0 | AGPL-3.0 |
| Stars / version | zEr0 (help us grow) | ~570 · v4.2.0 |
| Cost | Free — unlimited monitors, check rate, workers and status-page domains; 30 members by default | Free — unlimited |
| Stack | Single Go binary | Kotlin / JVM |
| Check types | 40 | 6 — HTTP, SSL expiry, heartbeat/cron, ICMP, TCP, DNS |
| Minimum interval | 10 seconds (browser checks 60 s, JS 30 s) | Adjustable |
| Multi-region checks | Distributed workers you run anywhere | 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 |
| Notification routing | 16 channels, per-check routing, SMS and voice through your own Twilio account | Per-monitor routing — email, Slack, Discord, Telegram, PagerDuty, webhooks |
| Status pages | Public, sections, custom domains, subscribers, Atom feed | Public and private, brandable |
| Maintenance windows | Yes | Yes |
| Config as code | YAML export / import / apply, REST API, sp CLI | YAML-declared monitors, full REST API |
| Observability exports | Prometheus | Prometheus and OTLP |
| DNS change detection | Up/down only | Drift alerts — notifies on a record change without flipping DOWN |
| AI / MCP | MCP server built in | MCP server (experimental, off by default) |
| Multi-tenant | Yes, with roles | No |
Where SolidPing is the stronger choice
Protocol coverage, by a wide margin. Kuvasz covers 6 check types; SolidPing covers 40. If you need to watch a database, a mail server, a message queue, a Kubernetes cluster, an SNMP device or a browser flow, Kuvasz simply does not go there. (Credit where due: Kuvasz added TCP and DNS in v4.2.0 and is closing ground — this was 4 types three weeks earlier.)
Checks from more than one place. Kuvasz runs as a single instance. SolidPing's distributed workers confirm an outage from several vantage points before paging you.
On-call. No rotations or escalation in Kuvasz.
More than one tenant. Kuvasz has no multi-tenancy or roles; SolidPing separates organisations and gives you read-only accounts.
A single binary with no JVM. Kuvasz is Kotlin on the JVM, which is fine but is a heavier runtime than a static Go binary if you are running it on a small box.
Where Kuvasz is the stronger choice
DNS drift detection is better than ours, and we should say so. Kuvasz alerts when a DNS record changes without treating it as an outage. That is a genuinely distinct alert class and SolidPing does not have it.
Private status pages. Kuvasz serves brandable status pages that are private as well as public. Ours are public.
OTLP export. Kuvasz exports both Prometheus and OpenTelemetry metrics; we export Prometheus.
Home Assistant. There is an official integration. For a homelab that is Home-Assistant-centric, that matters more than a feature table suggests.
Maturity in a small surface. Six years of releases on six check types means those six are very well worn.
The other model, on both sides
Kuvasz has no hosted service — it is self-hosted only.
SolidPing has one, running the same binary. SolidPing Cloud is free for 100 monitors and 10 checks a minute, then €5 / €15 / €45, probing from six shared regions. Going hosted re-attaches plan caps on monitors, check rate, seats, agents and status-page domains, and drops SMS, voice and WhatsApp, which only work when you supply your own Twilio account — so the self-hosted build you are comparing here is, on those axes, the more capable of the two.
Which should you pick?
Kuvasz is an excellent fit for a homelab or a small team that needs HTTP, TLS, ping, TCP, DNS and cron heartbeats, wants private status pages, and values a mature, focused tool. Its DNS drift alerting is a real reason to choose it.
SolidPing is the answer when the list of things you need to watch runs past those six protocols, when one vantage point is not enough, or when someone has to be on call.