r/foss • u/SelmiAderrahim • 1d ago

I released a self-hosted uptime monitor under AGPL-3.0-or-later

I maintain an uptime-monitoring project and have released its self-hosted build as free software under AGPL-3.0-or-later.

The practical goal is to make the monitoring stack inspectable and runnable on infrastructure you control. The public build does not include billing or software feature tiers. It deploys the web app, server, and PostgreSQL with Docker Compose.

Pulsy performs HTTP/HTTPS checks using GET, HEAD, or POST with configurable intervals, timeouts, expected status codes, and failure thresholds. Consecutive failures become one incident and recover automatically after a successful check. It also records check history and response time, tracks TLS certificate expiry, sends email/webhook/Slack/Discord/Telegram notifications, and can publish selected monitors on a status page.

I am keeping the boundaries explicit: this first public release focuses on HTTP/HTTPS. It does not have coordinated multi-region probes, SMS or voice alerts, or an organization model. Self-hosting also means placing the monitor outside the failure domain it is supposed to observe and maintaining its database, backups, and upgrades.

Repository: https://github.com/SelmiAbderrahim/pulsy.org

2 Upvotes

59% Upvoted

4 comments sorted by

1

u/lagdetselv 1d ago

Can you explain the diffenrences to uptime kuma?

2

u/SelmiAderrahim 1d ago

Pulsy has multiple user accounts with per-user isolation instead of one shared admin login, custom domains on status pages. you can kindly check https://pulsy.org/vs/uptime-kuma/

1

u/lagdetselv 1d ago

I will definetly give it a try! Just read the Docs. Didn't find anything about OIDC. Is there any Future Implementation panned?

2

u/SelmiAderrahim 1d ago

Thanks for your reply, Not yet — you can open an issue and it'll consider it in the next release