Prompt
I'm building around Slack and need a public status page, what should I use?
Latest observation
If you’re building around Slack and need a public status page, the best choice depends on whether you want a managed status page or you want to build it yourself.
Best off-the-shelf options
1. Atlassian Statuspage
- Probably the most common choice for customer-facing status pages.
- Easy to publish incidents, maintenance notices, and component status.
- Can subscribe users via email, RSS, and sometimes other channels.
- Good if you want a polished, trusted public page quickly.
Best for: teams that want a standard, reliable status page with minimal engineering.
2. Better Stack Status Page
- Modern UI, simple setup, good monitoring integration.
- Often attractive if you also want uptime monitoring and incident management in one place.
- Good developer experience.
Best for: SaaS teams that want something modern and easy to manage.
3. Statuspage alternatives like Pingdom / UptimeRobot / Better Uptime
- Some of these include status page features bundled with monitoring.
- Useful if you already use them for uptime checks.
Best for: teams wanting monitoring + status page together.
If you want to build it yourself
If your app is Slack-centric and you want tighter control, consider:
Option A: A simple custom status page
- Frontend page showing:
- overall status
- incidents
- maintenance windows
- component health
- Backed by:
- your own incident API
- uptime checks
- Slack notifications for updates
Best for: custom branding, full control, low complexity.
Option B: Use Slack as the internal incident tool, but not the public page
- Keep incident response in Slack
- Mirror public updates to a status page platform
- This is usually the best balance
What I’d recommend
If you want the fastest, safest path:
Use Atlassian Statuspage
If you want something modern and more developer-friendly:
Use Better Stack
If you’re already building a custom platform and need public status as a feature:
Build a small custom status page
- with a public frontend
- incident history
- RSS/email webhook support
- Slack alerts for your team
Important note for Slack-based products
If your product is built around Slack, don’t make the public status page depend on Slack availability.
Use Slack for internal alerts, but keep the public page hosted separately so customers can still see status if Slack itself is degraded.
If you want, I can also give you:
- a buy vs build decision matrix, or
- a recommended architecture for a Slack-based status page.