publicstatus is a status page for your services — the page you point customers to when something breaks. Publish incidents with a timeline, show per-component status, and keep a public history of past outages. It's self-hostable and hosted in the EU, so your incident data stays under your control and GDPR-friendly. A straightforward alternative to Statuspage or Instatus for teams who'd rather own their status page than rent it.
No reviews yetBe the first to leave a review for publicstatus
Maker
📌
Hey Product Hunt 👋
I built publicstatus because every status page tool I tried meant handing my incident data to a US SaaS — and a status page is the one thing you want to stay up, and stay yours, when everything else is on fire.
So this one is self-hostable and EU-hosted: incidents with a real timeline, per-component status, and a public history of past outages. Your data stays under your control, GDPR-friendly by default.
It's meant as a no-drama alternative to Statuspage or Instatus for teams who'd rather own the page they point customers to during an outage.
Happy to answer anything here — and I'd genuinely love to hear what would make you switch from your current setup.
Report
How do you handle notifications when an incident updates, and is there a way to pipe incidents into Slack or PagerDuty alongside the public page?
Report
Self-hosting was painless and the per-component view looks clean. The EU-hosted angle is a nice plus if GDPR keeps you up at night.
How do you handle notifications when an incident updates, and is there a way to pipe incidents into Slack or PagerDuty alongside the public page?
Self-hosting was painless and the per-component view looks clean. The EU-hosted angle is a nice plus if GDPR keeps you up at night.