I Open Sourced My AWS Fork of Uptime Kuma

I Got Tired of Paying Hundreds for a Status Page, So I Open Sourced My AWS Fork of Uptime Kuma

There’s a point where “hosted convenience” stops being convenience and starts being rent.

I hit that point with status page and uptime monitoring tools.

So I built and open sourced Uptime Kuma (AWS) — my AWS-focused fork of Uptime Kuma — to give myself a cleaner, cheaper, more ownable option.

GitHub repo: https://github.com/chrisk60331/uptime-kuma

The problem

A lot of uptime/status page products start cheap, look simple, and then quietly turn into another monthly bill you don’t want.

If all you need is:

• uptime monitoring
• alerting
• clean status pages
• solid control over your own deployment

…paying hundreds a month starts to feel ridiculous.

Especially when you already know how to run infrastructure.

What I built

Uptime Kuma (AWS) is an easy-to-use AWS-hosted monitoring tool based on Uptime Kuma.

It gives you a practical way to monitor services, trigger notifications, and publish status pages without handing yet another core operational function to a pricey vendor.

What it does

Core features include:

• Monitoring for HTTP(s), TCP, keyword checks, JSON query checks, WebSocket, Ping, DNS records, push, Steam game servers, and Docker containers
• Fast, reactive UI
• Notifications via Telegram, Discord, Slack, Gotify, Pushover, Email (SMTP), plus 90+ notification services
• 20-second monitoring intervals
• Multiple status pages
• Domain mapping for status pages
• Ping charts
• Certificate info
• Proxy support
• 2FA support
• Multi-language support

Why I open sourced it

Because this is exactly the kind of software that should be easy to inspect, run, modify, and own.

Infra tooling gets better when builders can:

• deploy it themselves
• adapt it to their environment
• avoid getting trapped in recurring SaaS spend
• improve it in the open

Open source keeps the leverage where it belongs: with the operator.

Why it matters

This isn’t just about saving money.

It’s about control.

If uptime monitoring and status communication are important to your business, you probably shouldn’t treat them like a black box subscription you barely control.

You should be able to:

• run it where you want
• understand how it works
• customize it when needed
• keep your costs sane

That’s the point of this project.

Built in the same spirit as what I’m doing with Backboard.io

I’m building more tools in and around Backboard.io, and the pattern is simple:

Build useful things.
Solve real problems.
Open source what should be open.
Keep the stack practical.

This project fits that exactly.

Getting started

Run locally:

./start.sh

Deploy:

./build.sh

Repo again:
https://github.com/chrisk60331/uptime-kuma

Final word

If you’re paying too much for uptime monitoring or status page software, this may be the shove you need to just run your own.

No pitch deck.
No “contact sales.”
No nonsense.

Just a solid open source AWS-hosted option.

If you check it out, fork it, improve it, or deploy it, I’d love to see what you do with it.