Kener

Kener puts up a clean status page without the weight of a full observability suite behind it. It is aimed at the team that needs to publish uptime and incident updates today and does not want to spend a week configuring Datadog or Atlassian tooling to do it.

The system is built with SvelteKit and Node.js, using shadcn-svelte for the interface. Its name comes from the Assamese word kene, meaning how is it going.

Monitoring, communication and administration all live in the same instance.

• Check types: API, ping, TCP, DNS, SSL, SQL, heartbeat and GameDig monitors.
• Incidents and maintenance: timelines, updates, acknowledgements and scheduled windows keep users informed.
• Notifications: alerts go out by email, webhook, Slack and Discord.
• Branding: logo, colors, custom CSS, themes, light and dark mode, localization and timezone-aware display.
• Team workflows: role-based collaboration, trigger-based workflows, template-driven messaging and API keys.
• REST API: programmatic access to incidents, monitors and reporting.

One instance can run several status pages, and embeddable widgets and badges push status into other sites. Deployment is a Docker Compose file that starts Kener with Redis, and prebuilt images include subpath variants for serving under a path such as /status. Without Docker it needs Node.js 24.14 or later, Redis, and a secret key and origin set before the first start.