Kener review
A self-hosted status system with broad monitoring and incident history, but email-only subscriptions.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
Kener is an open-source status page and uptime monitoring system for teams that want to run service-health communication themselves. It checks websites, APIs, network services, databases, containers, game servers, and other targets, then displays uptime, latency, and status history. Its scope suits teams that need more than a public availability page: incident timelines, planned maintenance, access controls, and multiple pages are part of the same system. Teams seeking a managed hosted service or a broader set of subscriber channels should compare alternatives.
Monitoring is a notable strength. Kener supports API, Ping, TCP, DNS, SSL, SQL, Heartbeat, GameDig, gRPC, Docker, and group monitoring, with configurable cron-based check scheduling. Incident records can include Markdown updates, state changes, resolution, and audit history. Maintenance can be one-time or recurring, with schedules using iCalendar RRULE. This combination fits teams that want service checks and operational context together, particularly when recurring maintenance and traceable incident changes matter.
Kener's self-hosted model offers control over deployment and presentation, including Docker or Node.js deployment, custom domains or subpaths, branding options, and role-based access control with custom roles and permissions. Email subscriptions cover incident and maintenance updates; alert delivery triggers include email, webhooks, Slack, and Discord. That distinction matters: teams needing SMS or other subscriber channels may prefer a status product with those options. Kener is documented as free and open source, with no paid plan structure described here, so it is a fit for teams comfortable managing their own deployment rather than buyers looking for hosted operations and broader subscriber delivery.
Kener pros and cons
- Where it wins
- Monitors APIs, networks, databases, containers, and other targets
- Incident timelines include state changes, resolution, and audit history
- Supports recurring maintenance, multiple pages, and role-based access
- Where it doesn't
- Self-hosting puts deployment and operations on the team
- Subscriber updates are documented for email, not SMS
- Alerts rely on email, webhooks, Slack, or Discord delivery
Kener fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update