Kener

Kener is a lightweight, self‑hosted status page platform engineered for developers who need a fast, modern solution without the overhead of enterprise monitoring suites. Built on SvelteKit for the frontend and Node.js for the backend, it delivers a highly responsive UI while keeping server‑side logic minimal. The application focuses on core status‑page functionalities—incident reporting, component monitoring, and subscriber notifications—while exposing a clean API surface for custom integrations.

• Component‑based status tracking: Define services, databases, or APIs as individual components with real‑time health metrics.
• Incident lifecycle management: Create, update, and close incidents with structured metadata (severity, affected components, timeline).
• Subscriber notifications: Email or webhook dispatches triggered on status changes, enabling automated alerts to customers or internal teams.
• Analytics & uptime: Dashboard displays 90‑day availability percentages and historical incident trends.
• Theme & layout flexibility: Light/dark modes, custom branding via CSS variables, and responsive design out of the box.

The choice of SvelteKit gives developers a highly performant UI with minimal bundle size, while Node.js ensures compatibility across Linux distributions. SQLite is ideal for small to medium workloads but can be swapped with PostgreSQL for higher concurrency or data durability.

• RESTful endpoints: CRUD operations for components, incidents, and subscribers (/api/components, /api/incidents, /api/subscribers).
• Webhooks: Register URLs to receive JSON payloads on incident updates.
• Webhook authentication: HMAC signatures for secure callbacks.
• GraphQL (experimental): Query component status and incident history with a single request.
• CLI tooling: kener-cli (bundled) for bulk data imports, export, and health checks.

Developers can extend the API by adding custom middleware in src/server.ts or augmenting Prisma models. The open‑source license (MIT) encourages community contributions and forkability.

• Self‑hosting: Run a single Docker container; no external services required.
• Scalability: Horizontal scaling via a load balancer is supported; SQLite can be replaced with PostgreSQL for multi‑node deployments.
• Persistence: Data is stored in a single .sqlite file or external DB; backup strategies are trivial (copy the file).
• Environment variables: Configure database URL, mail server credentials, and webhook secrets via .env.
• Health checks: /health endpoint for Kubernetes liveness/readiness probes.

The Docker images are optimized for size (under 70 MB on Alpine) and include a minimal Node runtime, making them suitable for edge deployments or serverless containers.

• Plugin system: Developers can drop custom Svelte components into the src/lib/plugins folder; they are auto‑registered via Vite’s dynamic imports.
• Custom dashboards: Override the default SvelteKit routes with your own UI while reusing the API.
• External monitoring: Integrate with Prometheus, Grafana, or external uptime services by pushing incident data via webhooks.
• Email provider hooks: Swap SMTP or use services like SendGrid by modifying the mailer module.
• Authentication: Optional JWT or session middleware can be added for protected admin routes.

These hooks make Kener a drop‑in replacement or an augmentation point within existing DevOps pipelines.

• Documentation: Comprehensive docs hosted at https://kener.ing/docs/, covering API reference, deployment guides, and troubleshooting.
• Type safety: Prisma schemas and SvelteKit’s TypeScript support ensure compile‑time correctness.
• Community: Active GitHub repo with >300 stars, frequent releases, and an issue tracker that accepts feature requests.
• Testing: Built‑in Jest tests for API endpoints and SvelteKit component snapshots.

The learning curve is shallow: a single docker run command launches the service, and the admin UI can be customized within minutes.

| Criterion | Kener | Competitors (e.g., Statuspage,