SolidPing vs Kener
If the public status page is what you care about most, pick Kener. It is a status page system first, with monitoring built in to feed it, and its pages are more customisable than ours: themes, custom CSS and JavaScript, several pages per instance, embeds, badges and RSS. Its own README says it is not here to replace Datadog or Atlassian, and it is honest about that.
SolidPing is a monitor first. It has status pages, but its weight is on check types, multi-region checks, alerting and on-call.
Kener is built by Raj Nandan Sharma and is MIT licensed. Facts below come from its repository and the docs shipped in it on 6 October 2026 (v4.1.6). It releases often. If we got a detail wrong, please open an issue.
At a glance
| SolidPing (self-hosted) | Kener | |
|---|---|---|
| License | AGPL-3.0 | MIT |
| Stack | One Go binary | SvelteKit and Node.js (24.14 or newer) |
| Database | SQLite or PostgreSQL | SQLite, PostgreSQL or MySQL |
| Other services | None | Redis is required |
| Check types | 40, including UDP, SMTP, IMAP, SSH, FTP, WebSocket, Kafka, MQTT, SNMP, seven databases and browser checks | 12: API, Ping, TCP, DNS, SSL, SQL, Heartbeat, GameDig, gRPC, Docker, Prometheus, Group |
| Scheduling | Down to 10 seconds | A cron expression per monitor |
| Multi-region | Workers and private agents you run anywhere | Not documented. Checks run from the Kener server |
| Alert channels | Email, Slack, Discord, Teams, Telegram, ntfy, PagerDuty, Matrix, Pushover, webhooks and more; SMS and voice through your own Twilio | Webhook, Discord, Slack, email |
| On-call & escalation | Rotations, overrides, multi-step escalation | No |
| Status pages | Public, sections, custom domains, subscribers | Several pages, themes, custom CSS and JS, i18n, embeds, badges, RSS |
| Subscribers | Yes | Email, OTP-verified, per-event preferences |
| Maintenance | Maintenance windows | Maintenance with recurring RRULE schedules |
| Users & SSO | Organisations, roles, OIDC, SAML, LDAP, Google, GitHub, GitLab, Microsoft | Admin, editor, member and custom roles; OIDC with group-to-role mapping |
| Hosted option | SolidPing Cloud | None |
| Automation | REST API, sp CLI, YAML apply, MCP server | REST API with API keys |
Where Kener is the stronger choice
The public status page. Theming, custom CSS and fonts, several pages, embeddable widgets and RSS. It is the product's focus and it shows.
Subscribers and maintenance. OTP-verified email subscriptions with per-event preferences, and recurring maintenance with RRULE.
Custom roles. Fine-grained permissions and OIDC group-to-role mapping.
MySQL. If MySQL is your house database, Kener runs on it. SolidPing does not.
Where SolidPing is the stronger choice
Check types. 40 against 12. Mail servers, message queues, SSH, FTP, SNMP and more have dedicated checks.
Alerting and on-call. Many more channels, plus rotations and escalation. Kener has four channels and no on-call.
Checks from several places. SolidPing runs workers and private agents wherever you put them. Kener checks from the one server it runs on.
Fewer moving parts. One binary on SQLite. Kener needs Node.js and a Redis.
A hosted option. SolidPing Cloud runs the same binary, with a free plan of 100 monitors. Kener is self-hosted only.
Which should you pick?
Pick Kener when the status page is the deliverable and a handful of monitors from one place is enough.
Pick SolidPing when monitoring and alerting are the job and the status page is one part of it. SolidPing has no Kener importer, so moving means recreating monitors through the dashboard, the API or a YAML file.