OmniFeed Search

Kener

Self-hosted status page system with built-in monitors, incidents and maintenance notices

Visit kener.ing
Screenshot of Kener
Kener, from kener.ing

Our verdict

#2 of 4 in Self-hosted uptime monitors · If customers read your status page

Pros

  • The fullest set of status page tools for keeping customers informed
  • Single sign-on through OpenID Connect and custom roles
  • Stores data in SQLite, PostgreSQL or MySQL

Cons

  • Alerts reach only webhook, Discord, Slack and email
  • Needs Redis, an in-memory data store, running next to the app

Who should skip:Anyone who wants alerts on Telegram, PagerDuty or SMS without writing a webhook.

Read the full review →

Rankings and alternatives

Self-hosted uptime monitors scores

Evaluated Nov 7, 2026 Evidence ↓
  • Components to run 3

    3/5 means: The app plus one required service, such as a database server or a cache

    Kener needs Redis next to the app; the database defaults to SQLite, so nothing else is required.

  • What it can check 4

    4/5 means: Eight of the nine

    API (HTTP), ping, TCP, DNS, SSL certificate expiry, SQL, heartbeat and Docker monitors make eight of the nine. Server CPU, memory and disk use are not documented.

    Rests partly on what the sources don't mention, which is a weaker signal than what they say.

  • Fastest check interval 3

    3/5 means: 1 minute

    Monitors run on cron expressions, and the shortest schedule shown is every minute.

  • Alert channels 1

    1/5 means: Fewer than 5

    Alerts go to four trigger types, webhook, Discord, Slack and email.

  • Public status pages 4

    4/5 means: Four of the five

    Several status pages from one install, incidents with a public timeline, scheduled maintenance shown to users, and email subscriptions plus an RSS feed. A custom domain per page is not documented.

  • Ways to manage monitors 2

    2/5 means: Two of the five

    Monitors are created in the admin panel or through the API. Configuration files and import or export of monitors are not documented.

    Rests partly on what the sources don't mention, which is a weaker signal than what they say.

  • Sign-in and users 4

    4/5 means: Three of the four

    Local logins, OpenID Connect sign-in and role-based access control are documented; two-factor login is not.

  • Getting data out 4

    4/5 means: Three of the four

    A REST API covering incidents, monitors and reporting, API keys for integrations, and badges and embeds. A Prometheus metrics endpoint is not documented.

  • Database choices 4

    4/5 means: A built-in database or two kinds of database server

    SQLite by default, or PostgreSQL or MySQL.

Evidence and sources

Self-hosted uptime monitors scores

Components to run 3 quotes
What it can check 3 quotes
Fastest check interval 1 quote
Alert channels 2 quotes
Public status pages 6 quotes
  • “Use Pages to create separate status views (for example: home, services, or infrastructure) and control which monitors appear on each page.”
    kener.ing/docs/v4/pages · checked
  • “Incidents are records for outages or degradations that affect one or more monitors. They provide a user-facing timeline of what happened, current status, and resolution progress.”
    kener.ing/docs/v4/incidents/overview · checked
  • “Maintenance windows in Kener allow you to schedule and communicate planned service disruptions to your users.”
    kener.ing/docs/v4/maintenances/overview · checked
  • “Let users subscribe to incident and maintenance email updates”
    kener.ing/docs/v4/subscriptions · checked
  • “Kener exposes a public RSS 2.0 feed of incidents and scheduled maintenance”
    kener.ing/docs/v4/rss-feed · checked
  • “Manage multiple status pages from one Kener instance”
    github.com/rajnandan1/kener · checked
Ways to manage monitors 2 quotes
Sign-in and users 2 quotes
  • “Kener uses a role-based access control (RBAC) system.”
    kener.ing/docs/v4/user-management · checked
  • “Use Manage → OpenID Connect to let users sign in via an external identity provider (Keycloak, Authentik, Azure AD, Okta, etc.) instead of — or in addition to — local username/password.”
    kener.ing/docs/v4/oidc · checked
Getting data out 3 quotes
Database choices 3 quotes

Facts

License 1 quote
Runs on 2 quotes
Needs 1 quote

Notability

Users 1 quote

Other quotes

Not cited by a score or fact 6 quotes