Consideration — OpenStatus (https://www.openstatus.dev/ )

[harshvardhan-yc]

🧭 Context

We are evaluating ways to provide public system status pages and incident reporting for our services. One option to consider is OpenStatus, an open-source status page framework that can be self-hosted and customized.

Link: https://www.openstatus.dev/

🎯 Why It Matters

• Improves transparency with users and partners
• Provides live status updates and incident history
• Reduces dependency on proprietary status page services
• Fits open-source philosophy (self-hostable and customizable)

🧩 Key Considerations

• Ease of setup & maintenance
• Integration with our current infrastructure/services
• Ability to automate status updates (from monitoring/alerts)
• Branding and customization options
• Access control and permissions (internal vs public views)
• Compatibility with planned observability stack

❓ Open Questions

• What SLA and uptime requirements do we need for the status page?
• Should the status page support authenticated internal status vs public?
• What data sources should feed the status updates?
• Should we integrate with alerts (e.g., PagerDuty, Prometheus Alertmanager)?