Kener is a free, MIT-licensed status page and uptime monitor that teams self-host with Docker. It combines service checks, incident timelines, maintenance windows, and subscriber notifications in one deployment, so a small team can run its public status communication without paying for a hosted subscription.[1][2][3]
Quick verdict
Small product and platform teams that need a branded public status page without paying for a hosted subscription will benefit most from Kener. Its concrete advantage is the combination: eleven built-in monitor types, incident timelines, maintenance windows, and subscriber notifications in one MIT-licensed Docker deployment. The material constraint is operational: you run the stack yourself (Kener plus Redis), and teams that need zero-setup hosted pages should choose something else. If you can run one Docker Compose stack and want monitoring and status communication together, choose Kener; if you need a managed page with no infrastructure, choose a hosted service such as Statuspage.[1][2][3]
Key features
Eleven monitor types with configurable checks Eleven documented monitor types, including API, Ping, TCP, DNS, SSL, SQL, Heartbeat, GameDig, and gRPC checks, with configurable check intervals and thresholds; inspect historical checks and uptime trends in the monitoring data explorer.[1]
Incident timelines with acknowledgements Create incidents with clear update timelines and acknowledgements, and standardize the wording with reusable message templates.[1]
Recurring maintenance windows Schedule one-off or recurring maintenance windows and keep subscribers informed before, during, and after the window.[1]
Trigger-based notifications Route alerts to email, webhooks, Slack, and Discord through trigger conditions, with a secrets vault for integration credentials.[1]
Multiple branded pages from one instance Run one status page per product, team, or region with custom logo, colors, CSS, and light and dark themes.[1]
Automation surface: REST API, keys, and embeds Drive incidents, monitors, and reporting through the full REST API, issue and revoke API keys, and embed status cards and badges in external sites and portals.[1]
Twenty-one languages with timezone-aware display Serve SEO-friendly public pages in 21 built-in languages with timezone-aware rendering for a global audience.[1]
Team access with roles and OIDC single sign-on Invite teams with role-based access, and sign users in through Keycloak, Authentik, Azure AD, Okta, or another identity provider over OpenID Connect with group-to-role mapping; OIDC and local accounts stay separate.[1]
Who will love it
Small teams dropping a hosted status subscription Small teams that only need status publishing, incident updates, maintenance windows, and subscriber notifications get all four from one free MIT-licensed deployment instead of a per-seat SaaS bill.[1][2]
Operators consolidating checks and communication Operators who currently pair a separate monitor with a separate status page can schedule eleven check types, post incidents, and notify subscribers from the same instance.[1]
Teams with an identity provider and self-hosting habit Organizations already running Docker and a provider such as Keycloak or Authentik get group-mapped roles and data on infrastructure they control.[1][2]
Who should avoid it
Teams that want zero infrastructure Teams unwilling to run Docker Compose with Redis, set secret and origin values, and own updates and backups should use a managed status page instead.[1]
Teams that need SMS or phone outreach The documented notification channels are email, webhooks, Slack, and Discord, so incident response built around SMS or paging needs a different tool.[1]
Teams shopping for deep observability Kener checks services and communicates status, and the project states it does not replace Datadog-style monitoring, so teams needing APM, tracing, or log analytics should look elsewhere.[1]
Questions worth asking
What is the best Kener alternative for non-technical users?
Is Kener really no-code?
How much does Kener cost per month?
Can you self-host Kener?
Yes. The project documents Docker and Docker Compose deployment with prebuilt images (including alpine and subpath variants), plus a Node.js path requiring Node.js 24.14 or newer with Redis. Before first start, set a strong secret key and set the origin to the public URL; the database persists in a mounted volume.[1][2]
Sources and editorial review
Source research. Reviewed on October 11, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- Kener documentation homepage
official · Observed October 11, 2026
Free open-source status page and uptime monitor; 11 monitor types, incidents, maintenance, notifications, roles, multi-page dashboards, REST API, 21 languages, branding, widgets, vault, triggers, templates, API keys.
- rajnandan1/kener repository
official · Observed October 11, 2026
SvelteKit and Node.js status page system; simple modern setup, not a Datadog or Atlassian replacement; Docker images, PaaS templates, Node 24.14 plus Redis path; name origin; sponsor links.
- Kener LICENSE
official · Observed October 11, 2026
MIT License, copyright 2026 Raj Nandan Sharma.
- Kener quick start
official · Observed October 11, 2026
Docker Compose path under 5 minutes on port 3000; KENER_SECRET_KEY and ORIGIN required; subpath via KENER_BASE_PATH; npm dev with Redis and auto migration plus seed.
- Kener OpenID Connect guide
official · Observed October 11, 2026
SSO via Keycloak, Authentik, Azure AD, or Okta with Authorization Code Flow plus PKCE; group-to-role mapping; OIDC and local accounts separate.