Overview:
Kener is an open-source, lightweight status page system built with SvelteKit and NodeJS. It provides a modern, customizable way to display the operational status of services and communicate incidents or maintenance to users. Designed for simplicity and minimal overhead, Kener allows teams to set up a branded status page without the complexity of larger monitoring platforms. It targets developers and operations teams seeking a straightforward, self-hosted alternative for service communication.
Core Features:
Monitoring Checks: Supports API, Ping, TCP, DNS, SSL, SQL, Heartbeat, and GameDig monitoring.
Incident & Maintenance Management: Create incidents with timelines and updates, and schedule maintenance windows with user notifications.
Notifications: Sends alerts via Email, Webhook, Slack, and Discord.
Customizable Status Pages: Allows branding with custom logos, colors, CSS, and themes, including light/dark mode and localization.
Multi-page Management: Manage and run multiple status pages from a single Kener instance.
REST API: Provides a full API for managing incidents, monitors, and reporting.
Use Cases:
Developers needing a lightweight status page: Set up a clean, modern UI to display service uptime without the weight of full monitoring suites.
Operations teams managing incidents: Create and communicate incident timelines and scheduled maintenance to internal or external users.
Teams running multiple services: Manage separate status pages for different products or environments from one centralized instance.
Integrating with existing workflows: Use the REST API for automated updates or trigger-based workflows for notifications.
Why It Matters:
Kener positions itself as a focused tool for service status communication, not a replacement for comprehensive monitoring platforms. Its value lies in being open-source, self-hosted, and free, allowing teams to maintain full data control over uptime history and incident reporting. The support for multi-page management, customizable branding, and integration with multiple notification channels makes it a practical, lightweight option for teams that want to avoid vendor-specific status page solutions.
