kener

Open-source status pages and uptime monitoring, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (MIT) status page and uptime monitoring system — a self-hosted alternative to Atlassian Statuspage that you deploy once and own forever [README][2].
• Who it’s for: Small teams and solo founders who need a professional-looking status page without paying $29–$1,400/mo to Atlassian. Especially relevant if you’re already paying for incident communication tools and want to consolidate [1][2].
• Cost savings: Atlassian Statuspage starts at $29/mo and scales to over $1,400/mo. Kener self-hosted runs on any VPS with Docker. Managed options start at $14/mo [2][docs].
• Key strength: The fastest path from “I need a status page” to “it’s live” in the open-source category — Docker Compose, under two minutes, genuinely [README]. The comparison table on the Kener docs page shows it leads on features against both free alternatives (Upptime, Uptime Kuma) and matches the paid incumbent on incident management [docs].
• Key weakness: Relatively small community (4,822 GitHub stars) compared to Uptime Kuma’s 60K+, and the incident management model that once relied on GitHub Issues has been replaced by a native system — but documentation for newer features lags the implementation [3][README].

---

What is Kener

Kener is a status page system built with SvelteKit and NodeJS. The pitch is direct: you want a good-looking status page with minimal setup overhead, you don’t want to pay Atlassian prices, and you don’t need the full observability stack of a Datadog or PagerDuty. Kener fills that gap [README].

The name comes from the Assamese word “Kene” — meaning “how’s it going?” — which is probably the most honest product naming in this category. That’s exactly what a status page does: it answers the question your users are already asking when your service goes down [README].

What distinguishes it from the obvious comparisons: Kener supports 11 monitor types (API, Ping, TCP, DNS, SSL, SQL, Heartbeat, GameDig, gRPC, and more), a full incident lifecycle with subscriber notifications, RRULE-based recurring maintenance scheduling, multi-page dashboards from a single instance, and a REST API with 17+ endpoints [docs]. That’s a materially richer feature set than either Upptime or Uptime Kuma, both of which are the usual free-tier alternatives [docs comparison table].

The project is solo-developed by Raj Nandan Sharma and sits at 4,822 GitHub stars with 267 forks. It’s been featured on both Awesome Status Pages and Awesome Self-Hosted, and deploys to Railway, Zeabur, and Render via one-click buttons alongside the standard Docker path [README][4].

---

Why people choose it

The reviews and managed-hosting write-ups converge on a consistent picture.

Versus Atlassian Statuspage. This is the comparison Kener wins on cost most visibly. Statuspage runs $29–$1,400+/mo depending on the plan, and the subscriber notification limits on lower tiers are a recurring frustration [docs]. Kener has no subscriber caps on a self-hosted instance — you notify as many people as you want [docs]. The LinuxLinks review [3] positions Kener as the natural choice for anyone who wants incident management without enterprise-tier pricing.

Versus Upptime. Upptime is GitHub-native — monitors run as GitHub Actions, incidents are GitHub Issues. That’s clever but limiting: you get one monitor type, no subscriber notifications, read-only API, and you’re fully dependent on GitHub uptime to report your uptime. Kener’s docs page makes the comparison explicitly, and it’s not close [docs]. The only scenario where Upptime wins is if you want zero infrastructure — no VPS, no Docker, no database.

Versus Uptime Kuma. This is the interesting fight because Uptime Kuma is the reigning open-source status page champion by star count (60K+ vs. Kener’s 4,822). Uptime Kuma has 10+ monitor types, broad notification channel support, and a large community. What it lacks is a full incident management lifecycle, RBAC, REST API coverage, and built-in subscriber notifications. If you need a status page that communicates incidents to customers — not just a dashboard you look at internally — Kener’s feature set is meaningfully ahead [docs comparison table][3].

The managed-hosting angle. The existence of multiple managed-hosting services for Kener (Elestio at $14/mo [2], Stellar Hosted at $49/mo [1]) says something about the market: there are teams who want the Kener feature set but not the DevOps overhead. For a non-technical founder, managed Kener at $14/mo vs. Statuspage at $29/mo is a simple decision.

---

Features: what it actually does

Monitor types (11 total):

• HTTP/API polling with configurable intervals down to 1 minute [README][3]
• Ping, TCP, DNS, SSL, SQL, Heartbeat, GameDig (game servers), gRPC [docs]
• Complex API chains with secrets injection [3]
• YAML-based monitor configuration with custom UP/DOWN/DEGRADED parsing logic [README][3]
• Default status override (e.g., defaultStatus=DOWN if no heartbeat received) [README]
• Push-based monitoring via REST API — useful for services that can’t be polled [docs]

Incident management:

• Full lifecycle: create, acknowledge, update, resolve [docs][3]
• Rich text incident updates with timeline [README]
• API-driven incident creation and management (17+ REST endpoints) [docs]
• Template-driven messaging for standardized communication [docs]

Notifications:

• Email, webhooks, Slack, Discord [docs]
• Trigger-based workflows — route alerts conditionally, not just on any status change [docs]
• Unlimited subscribers on self-hosted instances [docs]

Status page features:

• Multiple branded status pages from a single instance — one per product, team, or region [docs]
• Recurring maintenance windows with RRULE scheduling [docs]
• 21 languages with timezone-aware display [docs]
• Light/dark mode built in [docs][3]
• Embeddable widgets and badges for your own website [docs][3]
• 100% accessibility score — not a marketing number, it’s a stated design constraint [3]
• SEO-ready with server-side rendering [3]

Admin and operations:

• 3-role RBAC for team access control [docs]
• Secrets vault for integration credentials [docs]
• Monitoring data explorer for historical drilldown [docs]
• API key management for automation [docs]
• Analytics provider integrations: GA, Plausible, Mixpanel, Umami, Clarity [docs]

Deployment options:

• Docker (recommended), Docker Compose with Redis bundled [README]
• npm for bare-metal installs [README]
• One-click deploys to Railway, Zeabur, and Render [README]
• Kubernetes via base path configuration [README]
• Both Debian and Alpine Docker images available [README]

---

Pricing: SaaS vs self-hosted math

Self-hosted (Community Edition):

• Software license: $0 (MIT) [README]
• VPS: $5–10/mo on Hetzner, Contabo, or DigitalOcean
• Time to set up: under 2 minutes per the project’s own claim, realistically 30–60 minutes including domain + reverse proxy

Managed Kener:

• Elestio: from $14/mo — includes automated backups, SSL, updates, monitoring, custom domains, 24/7 AI DevOps support [2]
• Stellar Hosted: from $49/mo — dedicated instance, European and US datacenter options, 14-day free trial, no credit card required to trial [1]
• Stellar Enterprise: from €1,000/mo — SOC 2 Type II, ISO 27001, GDPR, dedicated SLA 99.99%, on-premise option [1]

Atlassian Statuspage (the incumbent):

• Hobby: $29/mo — 100 subscribers, limited monitor count
• Startup: $79/mo — 1,000 subscribers
• Business: $199/mo — 5,000 subscribers, custom domain
• Enterprise: $1,400+/mo — unlimited, SLA, SSO

Concrete math for a 10-person SaaS team:

If you’re on Statuspage Business ($199/mo) because you need a custom domain and >1,000 email subscribers, moving to self-hosted Kener on a $10 Hetzner VPS costs $10/mo — $2,268/year saved. If you’re non-technical and prefer managed, Elestio at $14/mo still saves $2,220/year compared to Statuspage Business, with no subscriber limits [2][docs].

The managed options from Elestio and Stellar are particularly interesting because they remove the single real argument for staying on Statuspage: “I don’t want to manage infrastructure.” At $14/mo for a fully-managed Kener instance, that argument evaporates [2].

---

Deployment reality check

The “under 2 minutes” claim for Docker deployment is credible — the repository ships a working docker-compose.yml that includes Redis, and the git-clone-to-running sequence is genuinely short [README]. This is not the same as saying it’s production-ready in two minutes.

What you actually need for production:

• A VPS with 1GB RAM minimum (2GB+ recommended with Redis)
• Docker and docker-compose
• A domain and reverse proxy (Caddy or nginx) for HTTPS
• An SMTP provider for email notifications
• A strong KENER_SECRET_KEY set in docker-compose.yml before first launch [README]

What’s straightforward:

• The Docker Compose path is well-documented [docs][2]
• Railway, Zeabur, and Render one-click deploys eliminate the VPS step entirely [README]
• The Elestio managed path requires no server management at all [2]

What can go sideways:

• The LinuxLinks review [3] was written against an older version that relied on GitHub Issues for incident management — that integration model has changed in v4. The documentation for v4 features is more complete than for earlier versions, but if you find tutorials online referencing GitHub-based incident creation, verify they’re current [3][README].
• The admin vault and trigger system are powerful but add configuration complexity beyond the basic status page use case. Plan an extra hour if you want smart alert routing [docs].
• Monitor types like GameDig (game servers) and gRPC are niche — they’re listed as features but aren’t well-documented in third-party sources. If you need them, test before committing [docs].

Realistic time estimate: 30–60 minutes to a production-ready instance for someone comfortable with Docker and a Linux terminal. For a non-technical founder following the docs: 2–4 hours including domain setup and SMTP. Or spend $14/mo on Elestio and skip the whole thing [2].

---

Pros and cons

Pros

• Genuinely MIT-licensed. No commercial license needed for self-hosting, white-labeling, or embedding in your own product [README].
• Best feature set in the free tier. Against Upptime and Uptime Kuma, Kener leads on incident management, RBAC, subscriber notifications, REST API depth, and maintenance scheduling [docs comparison table][3].
• 11 monitor types. HTTP, TCP, DNS, SSL, SQL, Heartbeat, gRPC, GameDig — not just “ping a URL” like simpler tools [docs][3].
• Unlimited subscribers. No artificial notification limits on self-hosted instances, unlike lower-tier Statuspage plans [docs].
• Multi-page from single instance. Run separate status pages per product, team, or region without running multiple servers [docs].
• Production-quality UI. SvelteKit + TailwindCSS, accessible (100% score), responsive, dark mode, 21 languages — this is not a hobby project’s interface [3][README].
• REST API with 17+ endpoints. Automate everything: incident creation, monitor management, reporting [docs].
• Cheap managed options. Elestio at $14/mo removes the infrastructure argument entirely [2].
• One-click cloud deploys. Railway, Zeabur, Render — no VPS required if you don’t want one [README].

Cons

• Smaller community than Uptime Kuma. 4,822 stars vs. 60K+ means fewer community tutorials, fewer third-party integrations, and a smaller support pool [README][4].
• Solo maintainer. Raj Nandan Sharma is the primary developer. This is a sustainability risk for anyone betting their incident communications on it long-term. There’s no company behind the project.
• Third-party review coverage is thin. The reviews available are mostly managed-hosting sales pages [1][2] and a single technical overview [3]. There’s limited independent long-term user experience data to draw from.
• Documentation lags features. v4 introduced significant changes (native incident management, admin vault, trigger system) and some older tutorials reference the GitHub Issues integration model that no longer applies [3].
• No native on-call rotation or escalation. Kener handles the communication side of incidents well, but it doesn’t replace PagerDuty-style on-call scheduling. You’d need a separate tool for that.
• GameDig and gRPC monitors are under-documented. Listed as features but sparse in third-party coverage — real-world reliability unclear [docs].

---

Who should use this / who shouldn’t

Use Kener if:

• You’re paying Atlassian $29–$199/mo for Statuspage and want to cut that line item permanently.
• You need a professional status page that handles real incident management — timelines, subscriber notifications, maintenance windows — not just a green/red dashboard.
• You’re comfortable with Docker (or willing to spend $14/mo at Elestio to avoid it entirely).
• You need to run multiple status pages — one per product, region, or customer — from a single self-hosted instance.
• MIT license matters because you’re embedding this in a client’s stack or your own product.

Skip it (pick Uptime Kuma instead) if:

• You only need an internal dashboard for your team to watch service health — not a customer-facing status page.
• You prioritize community size and tutorial abundance over feature depth.
• You want maximum notification channel variety — Uptime Kuma has broader notification integrations.

Skip it (stay on Statuspage) if:

• You need a guaranteed 99.99% SLA on the status page itself and don’t want to manage (or pay to manage) infrastructure.
• Your legal or compliance team won’t approve self-hosted infrastructure for customer communications.
• You need native integration with PagerDuty or OpsGenie in a supported enterprise configuration.

Skip it (pick Upptime) if:

• You want zero infrastructure — not even a $5 VPS — and GitHub Actions is sufficient for your monitoring cadence.

---

Alternatives worth considering

• Uptime Kuma — the community leader (60K+ stars). Better for internal monitoring dashboards, broader notification channels. Weaker on incident management, no subscriber notifications, no RBAC. Still free and MIT [docs comparison].
• Upptime — GitHub-native, zero infrastructure. One monitor type (HTTP), no subscriber notifications, no incident lifecycle. Best for static sites or projects already living on GitHub [docs comparison].
• Atlassian Statuspage — the paid incumbent. Better enterprise integrations, guaranteed hosting SLA, native Atlassian ecosystem ties. $29–$1,400+/mo. Closed source [docs comparison].
• Cachet — older PHP-based self-hosted status page. Kener’s feature set has surpassed it and Cachet has had long periods of low activity.
• Instatus — SaaS-only. Cleaner onboarding than Statuspage, competitive pricing, no self-hosted option.
• Freshstatus — free tier from Freshworks. Managed only, limited customization, but zero setup for non-technical teams.

The practical shortlist for a non-technical founder is Kener vs. Uptime Kuma vs. managed Statuspage. If you need customer-facing incident management with subscriber notifications: Kener. If you need an internal watchboard and don’t want to think about it: Uptime Kuma. If you need zero ops overhead and have the budget: Statuspage.

---

Bottom line

Kener is the right answer to a specific question: “How do I get a professional, customer-facing status page with real incident management, without paying Atlassian prices?” It beats every free alternative on features, and it undercuts every paid alternative on cost — including managed options at $14/mo that eliminate the DevOps overhead entirely. The trade-offs are real: smaller community, solo maintainer, no on-call scheduling, and documentation that’s still catching up with v4 features. But for a founder who’s been paying $79–$199/mo for Statuspage and realizing they use 20% of its features, Kener is a straightforward swap. Deploy it on Elestio for $14/mo and keep the $150+ for something that actually differentiates your product.

If you need someone to deploy and configure it for you, that’s a one-afternoon job — exactly what upready.dev does for clients who want the infrastructure handled once.

---

Sources

1. Stellar Hosted — Kener Managed Hosting — stellarhosted.com. https://www.stellarhosted.com/kener/
2. Elestio — Managed Kener as a Service — elest.io. https://elest.io/open-source/kener
3. LinuxLinks — Kener: Node.js status page tool — linuxlinks.com. https://www.linuxlinks.com/kener-node-js-status-page-tool/
4. OpenAlternative — Open Source Projects tagged “SvelteKit” — openalternative.co. https://openalternative.co/tags/sveltekit

Primary sources:

• GitHub repository and README: https://github.com/rajnandan1/kener (4,822 stars, MIT license)
• Official website: https://kener.ing
• Documentation and feature comparison: https://kener.ing/docs